10 plus ones
Shared publicly•View activity
View 15 previous comments
- 'And I'm not against RTTI. On the contrary' - exactly. This whole discussion has been a bit silly, hasn't it? 'I'm against RTTI abuse' - curiously enough, neither myself nor Stefan disagree with such a notion. What we disagree with is an insinuation that Delphi's language capabilities should be stuck at what they were in 2002.Nov 22, 2015
- I did not make such an insinuation. On the contrary, I wrote I use the extended RTTI, if available - but was able to find workaround for older versions of Delphi.
But I disagree with your insinuation ;) that Delphi's language capabilities of 2002 was not enough to write "modern" code, and apply SOLID or DDD principles. Everything needed was there, thanks to the great initial design of Delphi. Newest language evolutions, borrowed from C#/Java, were good, but IMHO not mandatory. And deprecating AnsiString or introducing ARC was IMHO a PITA. They came back from the "Delphi for .Net" for everyone. I'm happy I never used this target.
Insinuation war of non said / extrapolated / imagined ideas did began. :DNov 23, 2015
- DuckDuckDelphi is a very good example of utilizing Enhanced RTTI to help reducing a lot of code in situation where performance is not an issue - such as setting all UI controls to be readonly.Nov 23, 2015
- Why not just use a recursive loop setting the Enabled property, without RTTI?Nov 23, 2015
- Less code, while not reducing readable and performance. This is like asking JS coers: Why not just look through the DOM elements, without JQuery? :)Nov 23, 2015
- You are indeed comparing apples and oranges.Nov 25, 2015