Still some months before its actual release, there is nevertheless some good news – talk of the new compiler from official sources!
‘officials expect to begin shipping […] by the end of the year. Packaging and pricing have yet to be determined.’
The first question’s an obvious one:
Any idea how to get into the beta testing of this [new] Delphi?
Thoughts, however, quickly turn a touch negative, for it appears that not all traditionally bundled functionality will make the transition. Moreover, what about the support for a certain non-Windows OS, which is unfortunately missing from the released details about the upcoming release?
Should the omission […] cause me to lose all hope of ever finding Delphi, an excellent RAD environment, on […] an excellent OS?
As for what has been implemented, the news isn’t too hot either – for in a lame decision to follow what MS has done with their C compiler (don’t they even realise Delphi isn’t C?), they’ve kept Integer and Cardinal the same size changed the size of Integer and Cardinal!
I can resist no longer. What world do you come from? Certainly not Borland Pascal, which is what Delphi is!
A dogged defender of the Delphi team’s decision vainly tries to rationalise matters before being put in his rightful place:
You miss the point of the original post. Making new code work with old versions is NOT the point. The problem comes trying to use existing code written to [their own] standards.
Of course there are ways to modify old code to work with the new standards. But [they have] changed the standards. Why?
Why indeed? There is can only be one thing they could do that would rectify the situation. What? Why,
a compiler option that lets you choose
of course! But wait – this isn’t the biggest issue, not by a long shot, since they’ve only gone and changed the string type too! This means all code that does a certain not-so-uncommon thing with strings will have to be changed. As one commentator says:
I’ve seen LOTS of code that does this.
Me too. In fact, thinking about it, surely changing the string type would be so dumb, they just wouldn’t do it? I mean,
I should imagine so [i.e., that such code will have to be changed], but I sincerely doubt the new type will be simply called “string”.
Unfortunately, the official position to the contrary is quickly made clear. As if to rub salt into the wound, it is accompanied by this rather dubious claim:
We tried to make the transition as transparent as possible. Most code will convert straight across with no changes. Other will have to be modified slightly depending on how much they depended on the physical layout of the string.
‘Most’, ‘slightly depending’? Really now! As the voice of resigned reason puts it:
I am unconvinced that [they are] not making a big mistake to *redefine* old types and make new types constant. It does not make sense to me.
Discussion then ends on a weirdly appropriate note though:
There are some fairly obvious questions about the next release of Delphi that I have not seen discussed yet.
(1) When will it be available?
(2) Will the documentation be improved?
Happy New Year!
[For sure, I’ve made full use of my delete , full stop and square bracket keys. But then, my source is only a single thread…]