From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Can lisp functions have more than one point of return? References: <3226539899126540@naggum.net> <11Jp8.105423$Vl.3617235@typhoon.austin.rr.com> Mail-Copies-To: never From: Erik Naggum Message-ID: <3226610746933462@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 22 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, 01 Apr 2002 00:45:31 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1017621931 193.71.199.50 (Mon, 01 Apr 2002 02:45:31 MET DST) NNTP-Posting-Date: Mon, 01 Apr 2002 02:45:31 MET DST Xref: archiver1.google.com comp.lang.lisp:30651 * Zachary Turner | My question now is how natural is it to use return? Well, there are a few hints. Many forms set up a block named nil from which you can return with a simple return instead of return-from. This is particularly prevalent for the iteration constructs do, do*, dolist, and loop, so you can break out of a loop early. This is much cleaner than using an extra variable of heavier mechanisms locally. | So I'm wondering overall how much is return actually used? I think you should worry about this later and focus on learning the language and finding uses of the constructs you learn. Knowing when to use a construct is knowledge. Knowing when not to use a construct is wisdom. If you merely collect knowledge without much understanding, you will at least be skillful. If you merely collect wisdom without much understanding, you will only be immobilized. /// -- 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.