Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
ACL5beta: #'character
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Lyman S. Taylor  
View profile  
 More options Aug 5 1998, 3:00 am
Newsgroups: comp.lang.lisp
From: ly...@cc.gatech.edu (Lyman S. Taylor)
Date: 1998/08/05
Subject: Re: ACL5beta: #'character
In article <m37m0njezz....@mute.eaglets.com>,
Sam Steingold  <s...@goems.com> wrote:

>ACL5beta:
>user(8): (character 1000)
>nil
>user(9): char-code-limit
>65536

>Is this a bug?  

   More than likely. In the nitty gritty language lawyer parlance, no.
   The HyperSpec says that it "should signal an error".  This phrase in the
   glossary on error terminology:

http://www.harlequin.com/education/books/HyperSpec/Body/sec_1-4-2.html

   essentially means it only "has to" with the safety level turned all the way
   up. However, I have yet to see any of these kinds of "animals" change their
   "spots" when in fact you do pump up the safety level. In my experience,
   it is rare that environments have the "correct" version waiting in the
   wings to insert _only_ if the safety level is high.

--

Lyman S. Taylor           "Computers are too reliable to replace
(ly...@cc.gatech.edu)        humans effectively."
                                Commander Nathan Spring, "Starcops"


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Erik Naggum  
View profile  
 More options Aug 6 1998, 3:00 am
Newsgroups: comp.lang.lisp
From: Erik Naggum <cle...@naggum.no>
Date: 1998/08/06
Subject: Re: ACL5beta: #'character
* Sam Steingold <s...@goems.com>
| ACL5beta:
| user(8): (character 1000)
| nil
| user(9): char-code-limit
| 65536
|
| Is this a bug?  (looks like it; #'character should either return a
| character or signal an error, right?)

  CHARACTER does not take an integer argument in ANSI CL.

  I have to _guess_ that the implied question really is why the value of
  CHAR-CODE-LIMIT does not reflect the true limit, which is 256.  if this
  is so, see the standard's entries on CHAR-CODE-LIMIT and CODE-CHAR.  the
  latter _does_ take an integer argument, an _may_ return NIL.

  _always_ consult the specification.  there are no short-cuts.

http://www.harlequin.com/books/HyperSpec/Body/convar_char-code-limit....
http://www.harlequin.com/books/HyperSpec/Body/fun_code-char.html
http://www.harlequin.com/books/HyperSpec/Body/fun_character.html
http://www.harlequin.com/books/HyperSpec/Body/glo_c.html#character_de...

#:Erik
--
  http://www.naggum.no/spam.html is about my spam protection scheme and how
  to guarantee that you reach me.  in brief: if you reply to a news article
  of mine, be sure to include an In-Reply-To or References header with the
  message-ID of that message in it.  otherwise, you need to read that page.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »