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
comp.lang.lisp
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Newbie asking for help
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
 
Steven M. Haflich  
View profile  
 More options Jun 23 2000, 3:00 am
Newsgroups: comp.lang.lisp
From: "Steven M. Haflich" <hafl...@pacbell.net>
Date: 2000/06/23
Subject: Re: Newbie asking for help
Print | View thread | Show original | Report this message | Find messages by this author

Jochen Schmidt wrote:
> It works for me in cmucl (warning on the nondefined variable "nlines")
> It works in Allegro Trial Edition 5.0.1 for Linux (without warnings)
> It works in Lispworks Personal Edition 4.1.18 (without warnings)

Both Allegro and Lispworks have both interpreter and compiler.  I
believe both would signal a warning if the code were compiled, but
choose not to signal warnings in interpreted execution.  If they did,
the poor programmer would continually be harrassed by warnings when
executing typical debugging forms at the top-level listener, such as

  (setq foo ...)

BTW, in an earlier post Erik wrote:

  You're using a free variable, nlines, in this code.  You should not
  use a free variable unless you have very specific need for it.  This
  does not affect the correctness of your code, however.

I think this is incorrect.  Use of a free, undeclared variable name
is illegal.  See ANS 3.1.2.1.1.2 Dynamic Variables.  It happens that
every known implementation will treat a free reference to an undeclared
variable as if the variable had been declared special (and typically
warn in the compiler) but I know of nothing in CL semantics that requires
this.  Signalling error on reference to an undeclared free variable name
would also conform.  (That's what Java does, ;-)


 
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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google