|Re: (non) modifiable attributes... [message #1129101 is a reply to message #1128768]
||Tue, 08 October 2013 09:30
| Ed Merks
Registered: July 2009
On 08/10/2013 3:42 AM, Miles Parker wrote:
> It's not like we don't have enough meta-data to describe editability
> of features. There is volatile, transient, derived, changeable,
> unsettable. But none of them cover a case that comes up fairly
> frequently for me... allowing a value to be set once and only once.
So you need to prevent it being set a second time? Is there are
security issues involved?
> (It seems like changeable should cover this case, but instead it's for
> preventing setters altogether.)
> Maybe immutable would be a better name then (non) modifiable, but I'm
> wondering if any consideration was ever given to supporting something
> like this at the model level?
No. One question is whether something like this is for security reasons
or for bug detection because of course you can always only set it once
> (Maybe I've missed something embarrassingly obvious..)
Powered by FUDForum
. Page generated in 0.03009 seconds