Description Data - Properties Vs. Inst Vars

Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Description Data - Properties Vs. Inst Vars

Sean P. DeNigris
Administrator
Looking through the MADescription hierarchy, *almost* all field data is
stored as properties, except MAReferenceDescription>>#reference,
MAOptionDescription>>#options and a few others. Why these anomalies? Design
decision or mistake?



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Magritte-Pier-and-Related-Tools-f115649.html
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.list.inf.unibe.ch/listinfo/smallwiki
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Description Data - Properties Vs. Inst Vars

NorbertHartl
To me it is more a separation between mandatory and optional fields. If a class is called
ReferenceDescription it feels natural it has a reference instVar. Same for OptionDescription.

I don’t see the need for unifying anything.

Norbert


> Am 24.09.2018 um 19:31 schrieb Sean P. DeNigris <[hidden email]>:
>
> Looking through the MADescription hierarchy, *almost* all field data is
> stored as properties, except MAReferenceDescription>>#reference,
> MAOptionDescription>>#options and a few others. Why these anomalies? Design
> decision or mistake?
>
>
>
> -----
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Magritte-Pier-and-Related-Tools-f115649.html
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.list.inf.unibe.ch/listinfo/smallwiki

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.list.inf.unibe.ch/listinfo/smallwiki