On 12/14/09, mattschinkel <[email protected]> wrote: > > I would like jallib to have junk/null variables such as: > > jallib_null_bit > jallib_null_byte > jallib_null_word > jallib_null_dword > > > There are many libs out there that create variables that are used for > nothing. So, if you include say 4 libs in your project, and 2 > procedures of each lib require a null variable, you are wasting 8 byes > of memory. > > Another example, functions have return values, and you don't always > want the return value.
Hi Matt, That's correct. One option could be recosmetic the function as a procedure. Some functions in the libraries already have the procedure version. In this case, you have to var byte null, then > put "null = my_func()". Why not have a jallib null variable > "jallib_null_byte = my_func()". > > Another example would be that you may want a temporary variable to do > some calculation, then never use it again. use a local one, not a global. BTW, 3 second of compilation its easy for a dual core computer. In the old days it tooks up to 3-4 minutes under DOS for a medium size compilation.... Vasile (Wesley) -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
