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
Message from discussion Dangling Closing Parentheses vs. Stacked Closing Parentheses
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
 
Anthony Cartmell  
View profile  
 More options Mar 28 2000, 3:00 am
Newsgroups: comp.lang.lisp
From: "Anthony Cartmell" <AJCartm...@csi.com>
Date: 2000/03/28
Subject: Re: Dangling Closing Parentheses vs. Stacked Closing Parentheses

> For Anthony Cartmell, I don't know IDL, and I've already posted
> the opinion of an ICAD developer, but it seems to me that whether
> or not IDL rules should allow for dangling parens should be weighed
> heavily on whether or not a defpart is source-only, or whether it
> is possible by any means to get hooks into the source (by way of
> a code-walker, macroexpansion, or other debugging activity).  If
> the former, then it doesn't matter.  If the latter, then unless
> there have been extensions to ICAD's pretty-printer over CL's
> printer, the intermediate forms will look "wrong", because they
> will have no dangling parens.

ICAD is pretty much source-only (if I understand what you mean about being
able to print the thing to re-generate the source), as the real lisp code is
generated by the compiler from some fairly hefty macros, the main one being
defpart.  As far as I know there is no way to generate the code for a
defpart created object from the Lisp object itself.  You can view the code
in the ICAD browser but think that is done by storing fragments of source,
and I seem to remember it keeps the original layout.  I may be wrong, it's
never seemed to me a very useful thing to do.

ICAD is really an fairly object-oriented language that just happens to be
based on Lisp.  The basic structure of the code is proprietry, and it could
be implemented in any base language.  The only places Lisp appears are in
expressions and function definitions.

An interesting angle on the discussion, thanks!

Anthony
------------------
Anthony Cartmell
Application Architect
New Design Paradigm
Worthing, England
Tel. +44 1903 201084
E-mail: AJCartm...@csi.com


 
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.