marcov wrote:Or FC (one ascii value increase like C->D)
To be honest, such wordplay trying to imitate 1980's lore sounds a bit stale IMHO.
True. But it seems to be a constant jurisprudence that adding classes to a language makes a substantial jump. Take Python 2 -> 3. VB6 -> VB.Net. C -> C++ ..etc... (pascal -> delphi)
Maybe anyway in the case of FB, classes have always been a part of the plan, so it's more as we were running a temporary FB--, but it would lead erroneously to think that the current versions miss really anything, which is not right.
deltarho wrote:Perhaps we can liven things up a bit with a 1.06 release and get everyone on the same footing. <smile>
I only hope that 1.07 will bring us some overloadable FOR EACH instruction.
About FOR EACH x IN y,
A- if y is an array of T, and x a variable of type T, then the array should be read from its lowest bound to the uppers one.
B- if y is a pointer of type T ptr, then the last chunk of bits of the type T should be the next address. This means that this T type should be structured like this. Or the x will not know where to jump next. So the type T that fits well, in my opinion, is made of 2 chunks, a chunk of data, and an integer representative of an address in memory.
I see that like this! I may well be fooled totally ;)