Tourist Trap wrote: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)
C and C++ were by different people teams (in different eras), Pascal went to Object Pascal (also different people and eras).
Borland later renamed it to Delphi because "pascal" had too many "old" connotations (though critics say that Delphi was trademarkable, and (Object) Pascal not)
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.
Object support has been worked on for a while. I think one could argue for a major version update when you receive a milestone, but I don't see a reason to rename the language. Even if some other languages did.
Tourist Trap wrote: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 ;)
We have this in FPC (also .NET copycatism), note that you should think about if x should be assignable or not. It really complicates the overloadable concept