rob at robmela.com
Sat Oct 27 23:43:09 EDT 2007
Oh... now I get part of it... but still, is there a use case for
explicitly marking a class as Unmanageable, or is it just that this
already extant feature is available in case that need arises?
# Unmanageable classes include classes:
# * without serializable attributes
# * explicitly marked as Unmanageable (is Og::Unamanageable)
# * are polymorphic_parents (ie thay are used to spawn polymorphic
Robert Mela wrote:
> I don't get the use case for unmanageable. Why would one make a class
> an Og object but have Og manager not manage it?
> BTW, "unmanageable" means "impossible to manage", as in "out of
> control" -- could there be a better name for it? "notmanaged" or
> Nitro-general mailing list
> Nitro-general at rubyforge.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 116 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20071027/408744b4/attachment.vcf
More information about the Nitro-general