On Mar 11, 2010, at 4:15 PM, Colin Law wrote:
Hmm, does the id happen to be 4? ;-)
try:
irb> puts nil.id
I suspect you may well have hit the nail on the head, but why would
accessing nil.id in the code not generate the 'Called id for nil'
error? It does for me.
Colin
development mode versus something else? (I think the whiny NilClass is
only for development)
-Rob
Rob Biedenharn http://agileconsultingllc.com
[email protected]
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
