From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,85034d1ac78a66eb X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-03-12 12:39:41 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.mathworks.com!newstransit.mitre.org!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!dfw-service2.ext.raytheon.com.POSTED!not-for-mail Message-ID: <3C8E6775.42B547BE@despammed.com> From: Wes Groleau Reply-To: wesgroleau@despammed.com X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,es-MX,es,pt,fr-CA,fr MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada Operating System References: <3c77b476.322111671@news.cis.dfn.de> <3C88E0D1.89161C16@despammed.com> <3C8A3999.2000301@earthlink.net> <3C8B0191.3080705@mail.com> <3C8C3B72.5050107@mail.com> <3C8E3E02.4070108@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 12 Mar 2002 15:39:17 -0500 NNTP-Posting-Host: 151.168.144.162 X-Complaints-To: news@ext.ray.com X-Trace: dfw-service2.ext.raytheon.com 1015965580 151.168.144.162 (Tue, 12 Mar 2002 14:39:40 CST) NNTP-Posting-Date: Tue, 12 Mar 2002 14:39:40 CST Organization: Raytheon Company Xref: archiver1.google.com comp.lang.ada:21131 Date: 2002-03-12T15:39:17-05:00 List-Id: > > some associated package) failed to run when installed in a directory > > whose pathname contained blanks. This is excatly the kind of issue > > that leads to scripting problems - the piece of software fails to > > distinguish between blanks which are part of a name and blanks .... > > Where I have seen this, is not in Ada code. This was in the shell > script (gate?) that was used for GtkAda. Let's blame the right > software here, eh. For that matter, there were _two_ problems. 1. The script writer did not consider the possibility of a directory name containing a space. 2. The person who named the directory was not aware of how painfully some operating systems punish you when you have spaces in your file names (or didn't care) -- Wes Groleau http://freepages.rootsweb.com/~wgroleau