Standard MACRO Library

[stylin]

Agamemnus, I'm afraid I don't follow. Could you elaborate?

[Agamemnus]

Something that can make, say, "IF X IS NOT EQUAL TO 5" into "IF X <> 5".

[stylin]

How in any way would that be useful?

[Agamemnus]

Well..... it could be useful for...other...things...with spaces....

[marzecTM]

still sad...

i wonder how you are going about the deallocators. i can't see a generic way to do this for arbitrary udts that have, say dynamically allocated memory in them that could again point to other dynamically allocated memory ad infinitum

[stylin]

still sad...

i wonder how you are going about the deallocators. i can't see a generic way to do this for arbitrary udts that have, say dynamically allocated memory in them that could again point to other dynamically allocated memory ad infinitum

Dynamically allocated memory associated with a UDT is always the responsibility of the programmer to deal with. Even the STL will leak memory if we don't manually deallocate our resources. Currently, I'm jury-rigging constructor and destructor calls in the raw memory functions (in all implementations I've studied, the STL allocates memory and constructs objects on demand).

So basically, there's no difference than having classes except for the fact that the client must manually construct their objects (as opposed to merely initializing objects and having the compiler construct the object for you, ala C++, Java, etc.) A little cumbersome, to be sure, but hey - what can you do?

I just wish I knew what the syntax for classes is going to be when they finally get supported so I can start reworking the library; since it looks like templates are probably not going to be a reality, at least for a long while (years, I supppose), I won't feel too bad about committing the entire code-base to MACRO'd classes.