From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed1.bredband.com!bredband!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Getting the PID in CLISP Date: 24 Oct 2002 18:46:33 +0000 Organization: Naggum Software, Oslo, Norway Lines: 22 Message-ID: <3244473993093055@naggum.no> References: <3244460769462022@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1035485193 8201 129.240.65.5 (24 Oct 2002 18:46:33 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 24 Oct 2002 18:46:33 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:44590 * Sam Steingold | Now we will probably export it (thanks to Tim Bradshaw and Marc | Mertens for explaining how it can be generally useful). | What name do people prefer? | GETPID? PROCESS-ID? PID? ID? #:G123? My vote goes to both `process-idĀ“ and `getpidĀ“, which would be the names people would look for it under. | How is this question pertinent to non-CLISP-users? If you do not understand that, I have to explain the value of society to human beings to you. But I assume you are just obnoxious and that it should suffice to say that it is helpful to know by what name functions that should be available to all environments will be known. It is part of the community standards development process to share information. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.