Well, your question is not particularly clear.
Are you worried about caching? Obviously, what is evaluated and then cached (i.e., with action caching or page caching) will not be evaluated again until the cache is cleared.
Or are you worried that the default argument value that is cached when the method is defined and all subsequent calls may have the same value as the default value? In this case, your console testing was valid and @ Linux_iOS.rb.cpp.c.lisp.n (longest.name.evar) is correct - Ruby does evaluate this expression every time.
Out of curiosity, what made you doubt your own testing on the console?
steve
source share