To answer this you would need to look at the other code surrounding current_user, but a more direct answer is that using the symbol :false would not represent a boolean false.
You would need to dig deeper into the code to figure out why they did not want an actual boolean false. My guess is that it was a hack that they have since been able to implement in a cleaner way allowing them to use an actual boolean false value. In any case it's an internal implementation so either way should not affect your public use of their API (assuming you're not hacking around their API). Ruby Freak wrote: > I have a couple of projects with Restful Authentication > # Store the given user id in the session. > def current_user=(new_user) > session[:user_id] = (new_user.nil? || new_user.is_a?(Symbol)) ? > nil : new_user.id > @current_user = new_user || :false > end -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
