From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!deine.net!hamster.europeonline.net!newsfeed.europeonline.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: representing a network in lisp References: Mail-Copies-To: never From: Erik Naggum Message-ID: <3227258449796334@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 30 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Apr 2002 12:40:32 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1018269632 193.71.199.50 (Mon, 08 Apr 2002 14:40:32 MET DST) NNTP-Posting-Date: Mon, 08 Apr 2002 14:40:32 MET DST Xref: archiver1.google.com comp.lang.lisp:31223 * joachim@arti.vub.ac.be | I have an additional pobem now however, if I evaluate | | => (setf *print-circle* t) | T | | then *print-circle* remains nil: | | => *print-circle* | NIL This does not appear to be very likely. Do you restart a new listener between these two forms? | I use Allegro Common Lisp 6.0. In their documentation the variable | *print-circle* is part of the common-graphcs package wich does not exist | for linux systems. What nonsense. The _function_ named print-circle is a common-graphics feature, but the _variable_ named *print-circle* (note the asterisks) is part of standard Common Lisp. If you use the documentation for Allegro CL 6.0, at least follow the links and pay attention so you do not make it appear that you confusion is Franz's fault. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief. Post with compassion: http://home.chello.no/~xyzzy/kitten.jpg