Newsgroups: comp.lang.misc,comp.lang.lisp,comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!udel!gatech!bloom-beacon.mit.edu!cambridge-news.cygnus.com!news.cygnus.com!nntp!lord
From: lord@x1.cygnus.com (Tom Lord)
Subject: Re: Symbol space in Scheme v. Lisp
In-Reply-To: marcoxa@mosaic.nyu.edu's message of 25 Jan 1995 14:44:27 GMT
Message-ID: <LORD.95Jan25172939@x1.cygnus.com>
Sender: news@cygnus.com
Nntp-Posting-Host: x1.cygnus.com
Organization: Cygnus Support
References: <3fv8pn$llu@gort.oit.umass.edu> <3g0sah$ssc@agate.berkeley.edu>
	<3g1an2$cr@Mercury.mcs.com> <LORD.95Jan23185312@cygnus.com>
	<MARCOXA.95Jan25094427@mosaic.nyu.edu>
Date: Thu, 26 Jan 1995 01:29:33 GMT
Lines: 24
Xref: glinda.oz.cs.cmu.edu comp.lang.misc:20142 comp.lang.lisp:16508 comp.lang.scheme:11864



	marcoxa@mosaic.nyu.edu asks:

	Will the [Guile] project try to be "as compatible as possible" with
	Common Lisp?

There is no such goal for Guile.  In my post, i pointed out a way in
which Guile was different from, not similar to Common Lisp.  


	I wonder: will I have a 'defpackage' in Guile? Will I use the
	'::' and ':' notation to access symbols in other modules?

We do have packages which are not quite the same as the Common Lisp
entities of the same name (for instance, we change the
symbol->variable mapping instead of the string->symbol mapping).

We do not impose syntax on symbol names.  :: and : have no special
meaning in a symbol name in Guile.

-t


