Justin Ossevoort

My examples were pretty screwed up, here is a cleaned up version with example:

    require 'doodle'

    $counter = 0

    class Foo < Doodle
       has init_a...

oh and the first block should of course have read:

    f.has?(:simple_attr)       # => true
    f.valued?(:simple_attr)    # => false
    f.assigned?(:simple_a...

I've been mulling over this for some days, but for these cover the really essential introspection needs. The only possibly relevant one that's possibly missing ...

The clearer is great, that really complements the <.assigned?>

I agree that the ActiveRecord way is ugly for it really conflicts with the way you'd expect boole...

I see I didn't really state my intentions clearly. What I was looking for was something along the lines of lazy initialization. And neither nor really do that.

...

Ah I was wondering how to do that, I'm more used to traditional issue tracking systems which have a clear classification, but I can see how tags help to simulat...

Oh, and here is the way to currently work around this:

class Foo < Doodle
  @@serial = 0
  has :uid do
     default{ @uid = @@serial += 1 }
  end
end

x = Foo....

It would be nice if one could easily prevent the generation of the setter method. Perhaps something along the lines of Moose's 'is' property:

has :uuid, :is =>...

I used Moose under perl and there they used the concept of 'predicate' and 'clearer' methods (normally something like: has_X and clear_X). A predicate under rub...