Newsgroups: comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!udel!gatech!howland.reston.ans.net!pipex!uunet!heifetz.msen.com!zib-berlin.de!uniol!Johannes.Leveling
From: Johannes.Leveling@arbi.informatik.uni-oldenburg.de (Johannes Leveling)
Subject: [Q] Good style ?
Organization: University of Oldenburg, Germany
Date: Fri, 18 Nov 1994 09:27:54 GMT
Message-ID: <1994Nov18.093520.1709@arbi.Informatik.Uni-Oldenburg.DE>
Sender: news@arbi.Informatik.Uni-Oldenburg.DE
Lines: 48

I have a few questions about what is considered good style
in programming in Scheme.

1) defines
   a: use of nested defines
   b: named lambda / letrec
2) define syntax
   a: (define (foo bar) foobar)
   b: equivalent define using lambda
3) quoting
   a: (define foo 'bar)
   b: (define foo (quote bar))
4) quoting self evaluating expressions
   a: (cons foo 1)
   b: (cons foo '1)
5) list constructors 
   a: cons
   b: append
   c: list 
6) hiding information
   a: one main procedure, all others hidden
   b: all procedures visible
7) automatic evaluation
   a: call a procedure automatically when loading a file
      (meaning top level procedure call (foo bar) in file foobar.scm)
   b: the other way (let use call procedures from top level)
8) initializing variables
   a: (list foo bar)
   b: '(foo bar)
9) changing variables
   a: (set-cdr! foo bar)
   b: (define foo (cons (car foo) bar))

Please tell me what you think is good style, why, and how bad you
think it is 0=bad, 9=excellent.
(speed, portability, etc.)
Why : I am planning to write a style guide for programming in Scheme.
      
Suggestions, ideas, comments welcome!






-- 
email : Johannes.Leveling@Informatik.Uni-Oldenburg.DE
-------------------------------------------
