Andrew Martin wrote: >pekr wrote: > > >>I meant something bit different - not real rebol objects, but e.g. earlier >> >> >mentined accommodation class. System admin (not necessarily rebol >programmer) can say to himself one day - hey, this hotel has cinema inside. >Where should I put that? So he goes to "object" repository, selects hotel >class, and adds/describes "attribute" (field) of 'cinema-inside? type e.g. >That was what I meant by ability to extend "object" during the system >life-time ...Of course there can be consequences to it, like such field not >existing in former records - so ti may cause some difficulcy to query engine >e.g. > >I want and need users to be add or remove fields. A fixed system won't be >better than what we've got all ready. > Of course - but I have to yet see (and understand), what advantages it can offer, and mainly - how such advatage can be used for the good ...
>Unfortunately, one has to then hunt for the other instances of the object in >the net and delete them. It's far more simple and quicker to just clear the >block! (if necessary) then add in fields (Name Value pairs) as required. >Sure, if you're just storing a tree of objects your system will work, but >not if one has network of values. > > what do you mean by "network of values"? -pekr- >Andrew Martin >ICQ: 26227169 http://valley.150m.com/ >-><- > > > -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
