Creating a new format for help text and options

[chuggafan]

https://github.com/LADSoft/OrangeC/commit/02453f1f84b3b4cf9b8cb7336a372b8ca699f1af#r53508135

This comment describes an idea I have for reimaginging how to format our options, so that we can categorize options for narrowing down help, we can automagically add/remove options, describe what conditions options happen under, etc.

we can do this with a macro implementation similar to the one shown in the errorlist and thus vastly improve option organization and centralize help text for each program.

[LADSoft]

i was actually thinking about the fact the help is spread out over different compiler configuration files tonite...

[chuggafan]

I've begun some sembalance of work on this, I think in the doing of this I'm also going to pull out the FNV1A_class stuff from beintris to an outer file to allow for any class to use it, as I want to use the string as a reference to the error number without going through the expensive std::string constructor.

[LADSoft]

Sure. That sounds like a good thing to have more widely available too.

[chuggafan]

While doing review of the various errors, I found ERR_FUNC_NOT_THREAD_LOCAL, error 288, which says "Functions cannot be thread local", but the error level is of "WARNING", should this be an ERROR? I can change this on my side so that there's no merge conflicts.

[LADSoft]

it probably should be an error... go ahead and change it if you would.

[GitMensch]

Is this still open? @chuggafan if yes, can you edit the issue to be more explicit what the suggested changes are, please?