From haible@ilog.fr Tue Sep 1 02:57:24 1998 Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id CAA19584 for ; Tue, 1 Sep 1998 02:57:22 -0700 (PDT) Received: from ilog.ilog.fr ([172.17.4.22]) by sceaux.ilog.fr (8.8.8/8.8.7) with ESMTP id MAA12292 for ; Tue, 1 Sep 1998 12:05:01 +0200 (MET DST) Received: from jaures.ilog.fr (jaures.ilog.fr [172.16.1.81]) by ilog.ilog.fr (8.8.8/8.7.3) with ESMTP id MAA05292; Tue, 1 Sep 1998 12:04:57 +0200 (MET DST) From: Bruno Haible Received: (from haible@localhost) by jaures.ilog.fr (8.9.0/8.9.0) id MAA28389; Tue, 1 Sep 1998 12:04:57 +0200 (MET DST) Date: Tue, 1 Sep 1998 12:04:57 +0200 (MET DST) Message-Id: <199809011004.MAA28389@jaures.ilog.fr> To: clisp-list@clisp.cons.org Subject: Re: $ sign in path not recognized In-Reply-To: <199809010647.XAA17875@seagull.cdrom.com> References: <199809010647.XAA17875@seagull.cdrom.com> Leo Sarasua writes: > I think it would be a good idea to allow in a pathname all > characters which a given OS allows as normal names. So, for the DOS > version, it should allow the $ sign but not the %. Can you please give me the complete list of characters which should be allowed in DOS file name parts? a...z A...Z yes 0...9 yes - _ yes : / \ . these have special meaning for the pathname syntax % no, used for delimiting environment variables ; no, used for delimiting pathnames in pathname lists What about #\Space and !"#$&'()*+,<=>?@[]^`{|}~ ? Bruno From haible@ilog.fr Tue Sep 1 04:50:36 1998 Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id EAA20638 for ; Tue, 1 Sep 1998 04:50:34 -0700 (PDT) Received: from ilog.ilog.fr ([172.17.4.22]) by sceaux.ilog.fr (8.8.8/8.8.7) with ESMTP id NAA15457 for ; Tue, 1 Sep 1998 13:58:11 +0200 (MET DST) Received: from jaures.ilog.fr (jaures.ilog.fr [172.16.1.81]) by ilog.ilog.fr (8.8.8/8.7.3) with ESMTP id NAA10178; Tue, 1 Sep 1998 13:58:10 +0200 (MET DST) From: Bruno Haible Received: (from haible@localhost) by jaures.ilog.fr (8.9.0/8.9.0) id NAA02599; Tue, 1 Sep 1998 13:58:10 +0200 (MET DST) Date: Tue, 1 Sep 1998 13:58:10 +0200 (MET DST) Message-Id: <199809011158.NAA02599@jaures.ilog.fr> To: clisp-list@clisp.cons.org Subject: Re: $ sign in path not recognized In-Reply-To: <199809010647.XAA17875@seagull.cdrom.com> References: <199809010647.XAA17875@seagull.cdrom.com> The OS/2 version of clisp does not unduly restrict the characters in pathnames. You could try running this OS/2 version instead of the DOS version. (Yes, the OS/2 version runs on DOS as well.) Bruno From donc@ISI.EDU Tue Sep 1 10:34:12 1998 Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id KAA23854 for ; Tue, 1 Sep 1998 10:34:11 -0700 (PDT) Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by darkstar.isi.edu (8.8.7/8.8.6) with SMTP id KAA02119 for ; Tue, 1 Sep 1998 10:41:23 -0700 (PDT) Message-Id: <199809011741.KAA02119@darkstar.isi.edu> To: clisp-list@clisp.cons.org Subject: Re: Error Condition Re: Re: $ sign in path not recognized In-reply-to: Your message of "Tue, 01 Sep 1998 10:36:24 PDT." <13804.12428.154810.452605@ragged> Date: Tue, 01 Sep 98 10:41:21 PDT From: Don Cohen >Yes, clisp assumes that DOS filenames contain only alphanumeric characters, >dashes and underscores. That may be a little over-restrictive, but it helps >discovering typos. Yes, and also prevents you from doing certain things that you might actually want to or even need to. >On other systems $ introduces an environment variable, just like % on DOS. >What would you expect clisp to do if you try to create a file whose name >is "%PATH%" ? Expand the environment variable or not? I think we have to distinguish between what the file system allows and how various interpreters (e.g., command) use special characters. Clisp should deal with the file system only. It should not try to imitate the parsing of various other programs. I don't know exactly what the dos file system allows. I believe that in unix a file name can contain any character other than / (forward slash). I don't think clisp should address this issue at all. If the file system functions give you an error when you try to create a file with a strange name then clisp should give you an error, and otherwise it should do whatever the system does. From lsarasua@epo.e-mail.com Wed Sep 2 07:28:12 1998 Received: from E-MAIL.COM (e-mail.com [204.146.168.195]) by seagull.cdrom.com (8.8.8/8.6.6) with SMTP id HAA04865 for ; Wed, 2 Sep 1998 07:28:11 -0700 (PDT) From: lsarasua@epo.e-mail.com Message-Id: <199809021428.HAA04865@seagull.cdrom.com> Received: by E-MAIL.COM (IBM VM SMTP V2R4a) via spool with SMTP id 5581 ; Wed, 02 Sep 1998 10:35:48 EDT Date: Wed, 02 Sep 1998 10:35:48 EDT To: clisp-list@clisp.cons.org In-Reply-To: note of 01/09/98 11:04 X-Sender-Info: Leo Sarasua Tel. (31) 70 - 340 31 77 The Hague, NL lsarasua@epo.e-mail.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: $ sign in path not recognized I agree with Don that CLISP should not get into OS dependant functions. Don Cohen wrote... > I don't know exactly what the dos file system allows. > I believe that in unix a file name can contain any character other > than / (forward slash). > > I don't think clisp should address this issue at all. If the file > system functions give you an error when you try to create a file with > a strange name then clisp should give you an error, and otherwise it > should do whatever the system does. Anyway, if CLISP has to limit the characters which are valid in a file name, here is a list of them for DOS: >Can you please give me the complete list of characters which should be >allowed in DOS file name parts? > > a...z A...Z yes > 0...9 yes > - _ yes > : / \ . these have special meaning for the pathname syntax > % no, used for delimiting environment variables > ; no, used for delimiting pathnames in pathname lists > All these are correct. > What about #\Space and !"#$&'()*+,<=>?@[]^`{|}~ ? Of these last ones: The ones my DOS version found valid are: !#$&'()?@^`{}~? The invalid ones are: Space and "*+,<=>[]| Leo From hoehle@zeus.gmd.de Thu Sep 3 08:08:15 1998 Received: from mail.gmd.de (mail.gmd.de [129.26.8.90]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id IAA16325 for ; Thu, 3 Sep 1998 08:07:56 -0700 (PDT) Received: from zeus.gmd.de (zeus.gmd.de [129.26.145.1]) by mail.gmd.de (8.8.8/8.8.8) with SMTP id RAA06315 for ; Thu, 3 Sep 1998 17:15:41 +0200 (MET DST) Received: by zeus.gmd.de id AA11960 (5.67b8/IDA-1.5 for clisp-list@clisp.cons.org); Thu, 3 Sep 1998 17:14:52 +0200 Date: Thu, 3 Sep 1998 17:14:52 +0200 From: Joerg Hoehle Message-Id: <199809031514.AA11960@zeus.gmd.de> To: clisp-list@clisp.cons.org Subject: Re: $ sign in path not recognized > From clisp-list@clisp.cons.org Wed Sep 2 16:42 MET 1998 > >Received: from mail.gmd.de (postix) by zeus.gmd.de with SMTP id AA26629 > (5.67b8/IDA-1.5 for ); Wed, 2 Sep 1998 16:42:51 +0200 > Date: Wed, 2 Sep 1998 07:28:25 -0700 (PDT) > Reply-To: clisp-list@clisp.cons.org > Originator: clisp-list@clisp.cons.org > Sender: clisp-list@clisp.cons.org > From: lsarasua@epo.e-mail.com > To: Multiple recipients of list > Subject: Re: $ sign in path not recognized > X-Listprocessor-Version: 6.0 -- ListProcessor by Anastasios Kotsikonas > X-Charset: LATIN1 > X-Char-Esc: 29 > Content-Type: text > Content-Length: 1240 > > I agree with Don that CLISP should not get into OS dependant functions. > > Don Cohen wrote... > > I don't know exactly what the dos file system allows. > > I believe that in unix a file name can contain any character other > > than / (forward slash). > > > > I don't think clisp should address this issue at all. If the file > > system functions give you an error when you try to create a file with > > a strange name then clisp should give you an error, and otherwise it > > should do whatever the system does. > > Anyway, if CLISP has to limit the characters which are valid in a file name, > here is a list of them for DOS: > > >Can you please give me the complete list of characters which should be > >allowed in DOS file name parts? > > > > a...z A...Z yes > > 0...9 yes > > - _ yes > > : / \ . these have special meaning for the pathname syntax > > % no, used for delimiting environment variables > > ; no, used for delimiting pathnames in pathname lists > > > All these are correct. > > > What about #\Space and !"#$&'()*+,<=>?@[]^`{|}~ ? > Of these last ones: > > The ones my DOS version found valid are: !#$&'()?@^`{}~? > The invalid ones are: Space and "*+,<=>[]| > Leo > > From hoehle@zeus.gmd.de Thu Sep 3 08:13:01 1998 Received: from mail.gmd.de (mail.gmd.de [129.26.8.90]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id IAA16414 for ; Thu, 3 Sep 1998 08:12:48 -0700 (PDT) Received: from zeus.gmd.de (zeus.gmd.de [129.26.145.1]) by mail.gmd.de (8.8.8/8.8.8) with SMTP id RAA05902 for ; Thu, 3 Sep 1998 17:20:36 +0200 (MET DST) Received: by zeus.gmd.de id AA12038 (5.67b8/IDA-1.5 for clisp-list@clisp.cons.org); Thu, 3 Sep 1998 17:19:50 +0200 Date: Thu, 3 Sep 1998 17:19:50 +0200 From: Joerg Hoehle Message-Id: <199809031519.AA12038@zeus.gmd.de> To: clisp-list@clisp.cons.org Subject: Re: $ sign in path not recognized [sorry for previous email, tty command line / ed / operator braindamage] lsarasua@epo.e-mail.com wrote: > The ones my DOS version found valid are: !#$&'()?@^`{}~? > The invalid ones are: Space and "*+,<=>[]| Looks a lot like command.com (i.e. shell syntax) restrictions. Did you try these by compiling a C program that directly calls open("\"*+,<=>[]|","w") instead of copy config.sys *+,...| ? Jorg. From amoroso@mclink.it Wed Sep 16 04:38:32 1998 Received: from ammi.mclink.it (ammi.mclink.it [195.110.128.1]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id EAA08193 for ; Wed, 16 Sep 1998 04:38:25 -0700 (PDT) Received: from net145-045.mclink.it (net145-045.mclink.it [195.110.145.45]) by ammi.mclink.it (8.8.8/8.6.12) with SMTP id NAA12866 for ; Wed, 16 Sep 1998 13:47:48 +0200 (CEST) From: amoroso@mclink.it (Paolo Amoroso) To: clisp-list@clisp.cons.org Subject: Assembly language of CLISP's virtual machine Date: Wed, 16 Sep 1998 11:47:23 GMT Organization: Paolo Amoroso - Milan, ITALY Message-ID: <35fd6386.236883@mail.mclink.it> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Is there any documentation on the assembly language of CLISP's virtual machine, i.e. the one whose instructions are displayed by DISASSEMBLE? Thanks in advance. Paolo -- Paolo Amoroso From haible@ilog.fr Mon Sep 21 02:10:45 1998 Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id CAA11648 for ; Mon, 21 Sep 1998 02:10:43 -0700 (PDT) Received: from ilog.ilog.fr ([172.17.4.22]) by sceaux.ilog.fr (8.8.8/8.8.7) with ESMTP id LAA29047 for ; Mon, 21 Sep 1998 11:20:50 +0200 (MET DST) Received: from jaures.ilog.fr (jaures.ilog.fr [172.16.1.81]) by ilog.ilog.fr (8.8.8/8.7.3) with ESMTP id LAA09964; Mon, 21 Sep 1998 11:20:40 +0200 (MET DST) From: Bruno Haible Received: (from haible@localhost) by jaures.ilog.fr (8.9.0/8.9.0) id VAA12790; Sat, 19 Sep 1998 21:10:14 +0200 (MET DST) Date: Sat, 19 Sep 1998 21:10:14 +0200 (MET DST) Message-Id: <199809191910.VAA12790@jaures.ilog.fr> To: clisp-list@clisp.cons.org Subject: Re: Assembly language of CLISP's virtual machine In-Reply-To: <35fd6386.236883@mail.mclink.it> References: <35fd6386.236883@mail.mclink.it> Paolo Amoroso asks: > Is there any documentation on the assembly language of CLISP's virtual > machine, i.e. the one whose instructions are displayed by DISASSEMBLE? There is now a documentation of the instruction set at http://clisp.cons.org/~haible/packages-clisp-bytecode.html Greetings, Bruno From amoroso@mclink.it Thu Sep 24 09:21:42 1998 Received: from ammi.mclink.it (ammi.mclink.it [195.110.128.1]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id JAA22468 for ; Thu, 24 Sep 1998 09:21:21 -0700 (PDT) Received: from net145-042.mclink.it (net145-042.mclink.it [195.110.145.42]) by ammi.mclink.it (8.9.1/8.9.0) with SMTP id SAA08872 for ; Thu, 24 Sep 1998 18:31:51 +0200 (CEST) From: amoroso@mclink.it (Paolo Amoroso) To: clisp-list@clisp.cons.org Subject: What's the purpose of .lib files? Date: Thu, 24 Sep 1998 16:32:11 GMT Organization: Paolo Amoroso - Milan, ITALY Message-ID: <360a3d0b.35259@mail.mclink.it> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit What is the purpose of the .lib files generated by the compiler? Paolo -- Paolo Amoroso From haible@ilog.fr Thu Sep 24 09:54:41 1998 Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id JAA23030 for ; Thu, 24 Sep 1998 09:54:37 -0700 (PDT) Received: from ilog.ilog.fr ([172.17.4.22]) by sceaux.ilog.fr (8.8.8/8.8.7) with ESMTP id TAA21389 for ; Thu, 24 Sep 1998 19:05:13 +0200 (MET DST) Received: from jaures.ilog.fr (jaures.ilog.fr [172.16.1.81]) by ilog.ilog.fr (8.8.8/8.7.3) with ESMTP id TAA25840; Thu, 24 Sep 1998 19:05:12 +0200 (MET DST) From: Bruno Haible Received: (from haible@localhost) by jaures.ilog.fr (8.9.0/8.9.0) id TAA19531; Thu, 24 Sep 1998 19:05:12 +0200 (MET DST) Date: Thu, 24 Sep 1998 19:05:12 +0200 (MET DST) Message-Id: <199809241705.TAA19531@jaures.ilog.fr> To: clisp-list@clisp.cons.org Subject: Re: What's the purpose of .lib files? In-Reply-To: <360a3d0b.35259@mail.mclink.it> References: <360a3d0b.35259@mail.mclink.it> Paolo Amoroso asks: > What is the purpose of the .lib files generated by the compiler? The .lib files contain definitions that may be needed for compiling other files. Suppose you have a file A.lsp, defining functions, macros, constants etc. And you have a file B.lsp, which contains a (require 'A) statement, because it uses some things defined by A.lsp. Then compilations of B.lsp will profit from a file A.lib, generated by a previous compilation of A.lsp. The benefit is threefold: - You don't need to have A loaded in order to compile B. If memory is tight, and if A contains only few inline functions, macros or constants, this is a space and time saver. If A.lsp does a lot of initializations or side effects when being loaded, this is important as well. - You don't need to have A loaded in order to compile B. You don't even have to *think* about A when loading or compiling B. - Suppose A.lsp is changed rarely, and B.lsp is changed frequently. It would be a waste of time to compile both A and B every time. The .lib file ensures that A is compiled only when needed. Bruno