Objects vs advanced records

[LemonParty]

Hello.

What is preferable to use old-school object or advanced records? What advantages and disadvantages?

[Thaddy]

objects support OOP although different syntax from classes.
records do not support OOP, no inheritance, not even with advanced records.

In general I use records for new code (with the exception of KOL) and use objects if I need a stack-oriented approach because then objects can be much, much faster than classes.

[Warfley]

Objects have inheritance and virtual methods. Records have variant parts, can overload operators and have management operators.

So if you need inheritance go with objects, for everything else records are probably the more versatile choice

[Awkward]

Question is why developers still didn't realize things what we have in records, even helpers for objects?

[LemonParty]

Are there a managment operators for objects?

[Thaddy]

Are there a managment operators for objects?

No, and they are not necessary because objects have constructors and destructors. Contrary to records, objects are not a flat model.
The way that works is a bit quirky to anyone under 55, but an established way that the old TP5.5 programmers are familiar with.

[Warfley]

Question is why developers still didn't realize things what we have in records, even helpers for objects?

Simple, objects aren't really touched. The only time objects get new features is if those are part of the shared functionality between objects and classes (or even records, all three share a lot of code in the compiler) and objects basically get that "for free".

There is no interest by the core developers to add change anything in objects that goes beyond that.

[PascalDragon]

Question is why developers still didn't realize things what we have in records, even helpers for objects?

Simple, objects aren't really touched. The only time objects get new features is if those are part of the shared functionality between objects and classes (or even records, all three share a lot of code in the compiler) and objects basically get that "for free".

There is no interest by the core developers to add change anything in objects that goes beyond that.

Well, I do plan to add helpers for objects, but mainly because I want to allow helpers for all types in the end.

[Martin_fr]

Well, I do plan to add helpers for objects, but mainly because I want to allow helpers for all types in the end.

What about generic constraints?

Code: Pascal  [Select][+][-]

1. //Instead of
2. generic Foo<X: class> = class(X) {...} end;
3. // Allow
4. generic Foo<X: object> = object(X) {...} end;
5.  

[PascalDragon]

Well, I do plan to add helpers for objects, but mainly because I want to allow helpers for all types in the end.

What about generic constraints?

While I do plan to extend generic constraints I don't intend to add constraints for objects.