Is there anyone with interests the Delphi language improvements ?.
Is there anyone with interests the Delphi language improvements ?.
e.g., string support in case statement, inheritance helper, improvement property syntax like a c#, support nullable type...
Someday, hope to see in the roadmap.
ps. Dear all. Nowadays, while I studying English. Please understand that english writing is wrong. Thank you :)
e.g., string support in case statement, inheritance helper, improvement property syntax like a c#, support nullable type...
Someday, hope to see in the roadmap.
ps. Dear all. Nowadays, while I studying English. Please understand that english writing is wrong. Thank you :)
I think nullable type is on the list. I will let Marco confirm this one.
ReplyDelete/sub
ReplyDeleteDavid Intersimone I guess they could be easily implemented using generics, and Allen Bauer wrote about it some years ago https://plus.google.com/u/0/+HoracioJoseCavalcantiFilho/posts/2vzP8sdF4f7
ReplyDeleteUsing variants (available since earlier versions of Delphi), you have nullable values within the language. They are pretty standard, efficient, and easy to work with. For instance ,we handle such value types in our ORM - see http://blog.synopse.info/post/2015/09/25/ORM-TNullable%2A-fields-for-NULL-storage
Also be aware that in the Delphi community, if you speak of "nullable types", you find people shortly trolling about "FreeAndNil" and that an object should never be nil. https://forums.embarcadero.com/thread.jspa?messageID=778868#778868 You have been warned! ;)
I am not sure I'd want the same syntactic sugar that C# has for properties. I think that Delphi does not really need it because Ctrl+C does most of the job. What I would REALLY be happy to see, though, is a small change whereby completing a class at cursor with a newly declared property uses a field for the set as well. I think the fact it's using an accessor method may entice developers to put stuff there that shouldn't be.
ReplyDeleteAndrea Raimondi you meant SHIFT-CTRL-C, right?
ReplyDeleteDorin Duminica possibly, yeah :D I meant Class Completion :)
ReplyDeleteAndrea Raimondi I use a template to create such a property. http://pastebin.com/zk08EMcV
ReplyDelete/sub
ReplyDeleteJungHwan Jang According to the roadmap, the Godzilla 10.2 release, will, possibly (I hope :D), include new language features (you can see "including language support" in the right side).
ReplyDeleteNullable types would be great David Intersimone Id also like to see async/await or something similar to that.
ReplyDeleteDavid Intersimone I am looking forward to nullable types, but besides them I would also like to see some related compiler features that would make it easier to work with such types.
ReplyDeleteLike null coalescing operator, optional chaining and similar. Actually, I would like to have those for reference types too.
Mike Margerum Some way to emulate async/await (using OTL, I think it should work also with System.Threading) http://www.thedelphigeek.com/2012/07/asyncawait-in-delphi.html
ReplyDeleteAndrea Raimondi I prefer less verbosity and ceremony in source code over "IDE vomit" (aka code/class completion) any day.
ReplyDeleteDavid Berneda Not very efficient though.
ReplyDeleteAs David Intersimone mentions, nullable types are on our internal language roadmap... not 100% sure what you mean by inheritance helper.
ReplyDeleteIn any case, there are many open feature requests on quality.embarcadero.com, and they are being evaluated
Marco Cantù Whoops, The word choices was wrong. It means the record helper supports "ancestor list" like a Free Pascal or Class Helper. And I will post the issue on quality portal as you mentioned. Thank you.
ReplyDelete