Great, thanks for confirmation.

As you certainly know this line is technically not necessary: ...

I usually use it anyway (but not always) to emphasize that it's only done when an image was allocated, but you're right, I know that.

What do these pXXXX variable names in Fl_Image_Reader mean? p like private? I do not see this scheme used in the other FLTK files.

I don't know either. It's not the official FLTK coding style, but sometimes contributed code doesn't conform to it. Private member variables should have a trailing underscore instead. Personally I think the 'p' is a bad choice, it could mean private, public, protected, pointer, ..., maybe more. I chose to keep the existing style and added the new variables with a 'p' prefix as well to avoid changing too much unrelated code but I'm not happy with this. BTW: the CamelCase variable names in Fl_GIF_Image are also not FLTK style.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.