| |
| |
On 2/19/21 10:16 PM Bill Spitzak wrote:
I think the question is whether a program can do anything useful with
those return values.
After all discussions here I'd say nobody sees a real useful application
of these variables.
The only use I can see is for a "glxinfo" type program to print out how
fltk has been compiled.
I agree, this would be a useful FLTK utility program (flinfo, maybe?).
If this is useful I would prefer it to be much more obvious that these
are compile-time constants. Ideally there is a structure defined, and a
single extern instance. This is compiled with a static assignment to a
value that is controlled by #if statements.
I do also agree that such a structure would be fine. This structure
would include much more (and different) values than what we have now.
We'd need a different implementation anyway, so I strongly believe that
we should remove the entire file config_lib.h and all variables (global
runtime config) associated with this file.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/af5b61f8-f117-3a47-390f-36b1603b700b%40online.de.
[ Direct Link to Message ] | |
|
| |
