The docs say what characters are guaranteed future-safe for *you* to
use in symbols, nothing more. I don't see what's so puzzling about
this.
On Apr 4, 8:33 pm, Douglas Philips d...@mac.com wrote:
(This is a follow up to my query last week, where upon I didn't fully
connect these dots)
On 2010 Apr 5, at 3:49 AM, ataggart wrote:
The docs say what characters are guaranteed future-safe for *you* to
use in symbols, nothing more. I don't see what's so puzzling about
this.
I asked a specific question:
Is it really still an open question that the comparison functions
would be
Oh yeah, we should fix the reader page to acknowledge that we've
used these characters in symbols already
The reader already has a macro associated with \, the character
literal.
user= (int \)
62
user= (str \)
user= (first )
\
HTH,
Sean
On Apr 5, 11:19 am, Douglas Philips d...@mac.com wrote:
On 5 April 2010 17:25, Sean Devlin francoisdev...@gmail.com wrote:
Oh yeah, we should fix the reader page to acknowledge that we've
used these characters in symbols already
The reader already has a macro associated with \, the character
literal.
user= (int \)
62
user= (str \)
user=
On 2010 Apr 5, at 4:15 PM, Michael Wood wrote:
I think his question should be read as if he had not included any
backslashes anywhere. i.e. he's asking about , , and =. Not \ or
\ etc.
Well, I was/am trying to be precise.
Symbols are looked up by strings and strings contain characters,
