-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flags system #213
Comments
There are a couple of open flag slots in the v3 branch -- I am still working on a way to expand the flags array given the limitations of C (there times when Pascal packed arrays would be really useful) that is efficient, fairly space-thrifty, and not so horrifically kludgy that it would make my brain snap when trying to debug it. |
Okay, v3 how has a *new* and *improved* flags arrangement, not documented (but look at the various sample programs for how to interact with the flags) and has broken the entire user interface. I may go back in and build a compatibility layer so that old binaries will continue to work (via appending _v3 to all of the changed interfaces, a shim module that has the old interfaces and remaps them to the new, then a whole wad of #defines that alias the _v3 names back to the older names for the illusion of compatibility.) |
Intresting, thanks for notification. |
I'm finally updating the documentation, and will close this issue when it's done. |
I have been prepared a pull request, which need a flag for this, but it looks like all possible slots busy. @Orc, that do you think about it, how new flags could be added now?
The text was updated successfully, but these errors were encountered: