TJF wrote:IMO the 'extents'/'inherits' question should be seen from a practice point of view. Which one makes it easier to translate code from the most used other languages (C/C++ ATM).
When FB can support all C/C++ features in an UDT it makes sense to have the same keyword. When an FB UDT has to get reviewed after the translation it makes sense to use another keyword.
The "basic" issue I have with that is that FB is not C/C++. It syntax style is BASIC... It's even easier to translate from/to FB/C++ if the syntax was exactly the same. :P
marcov wrote:Well, I'm biased of course, but if you recycle class, you can use parentheses:
Descendant = class(parentclass)
Descendant = interface(parentinterface)
abstract and similar keywords (sealed, deprecated,platform,abstract) appear before class/interface kw.
There is no specific use for either class or interface yet... can't call it recycled quite yet! Anyway, where exactly would you implement this? Like this?
Code: Select all
type mytype = class(myparenttype)
It wouldn't look pretty with both that and a "FIELD=" statement.