Re: Odd behavior calling a fn "test" or "try"

2011-01-11 Thread Daniel Werner
On Jan 11, 2:28 am, Tom Hall wrote: > I know I should not be naming my functions the same thing as ones in core You can and should, as long as it makes your life easier and doesn't get too confusing for readers. Just make sure you're able to access the original core bindings if you need them: (n

Re: Odd behavior calling a fn "test" or "try"

2011-01-10 Thread Chas Emerick
To expand on this: user=> (defn try [] 5) #'user/try user=> (try) ; `try` alone is resolved to the special form nil user=> (#'try) ; obtaining the `try` var works just fine ; (vars currently delegate function calls to their values) 5 user=> (@#'try) ; explicitly deref'ing the fn fro

Re: Odd behavior calling a fn "test" or "try"

2011-01-10 Thread Tom Hall
On Tue, Jan 11, 2011 at 1:51 AM, Stuart Halloway wrote: > Hi Tom, > > "try" is a special form, and "test" is a function. > > Stu Cheers Stu, should have thought of that. Am I correct in thinking only 3 possibilitys for "try" in (try 1) special form, macro, function ? Are the special forms imple

Re: Odd behavior calling a fn "test" or "try"

2011-01-10 Thread Stuart Halloway
Hi Tom, "try" is a special form, and "test" is a function. Stu > I know I should not be naming my functions the same thing as ones in > core but was surprised when I wrote the following > https://github.com/thattommyhall/tth-SICP/blob/master/1-35.clj > I have being doing the SICP stuff in clojur