>>9
i am a poor c-tard, explain how these 50-odd iterators would work for me?
more ideas:
the parsing of nulltermstrings will be done by functions like NulltermstringToUint, which will take the uintNulltermstringToUintSource'th character of nulltermstringNulltermstringToUint and place it in uintNulltermstringToUintDestination.
however, there will also be a stackstring datatype in which strings are uints stored on a stack. stackstrings can then be parsed by popping between stacks, analysing and modifing as we go.
(and now that we've defined string handling functions, we can write quines!)
obviously, converting between types is not automatic, but must be done with functions. uintNumber:==sintNumber is an error, we must use the UintToSint function.
allocating memory has been done, and i like the idea of using strictly segmented memory, and allocating only single segments, but the segment size should probably be something more like 256 (or 16?) bytes rather than 4K, as this would make string handling much more difficult.
another thing that should be worked out is memory deallocation. should this just use another function (e.g. free() in c), or can we come up with a better method?
oh, and we should probably have a method of self-modification.
finally, we still need a name for this language. i've been calling it 4code as a working name, but that's not a very impressive name