Date:	Mon, 30 Mar 92 09:10 EST
To:	99clifto AT lab DOT cc DOT wmich DOT edu
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
From:	Jose DOT Hernandez AT adi_email DOT analog DOT com
Subject:	Returned mail: Cannot send messa

 
 
Status: O

-------------( Forwarded letter follows )-----------------------
 
Date: Saturday, 28 March 1992  2:36am
Date: Sat, 28 Mar 92 02:41:20 EST
From: Mailer-Daemon AT nwd2sun1 DOT analog DOT com (Mail Delivery Subsystem)
Subject: Returned mail: Cannot send message for 3 hours
To: Mailer-Daemon
 
   ----- Transcript of session follows -----
 
   ----- Unsent message follows -----
Return-Path: <Mailer-Daemon>
Received: by nwd2sun1.analog.com (4.1/SMI-4.1)
 id AD10286; Fri, 27 Mar 92 22:44:46 EST
Date: Fri, 27 Mar 92 22:44:46 EST
From: Mailer-Daemon (Mail Delivery Subsystem)
Subject: Returned mail: Cannot send message for 3 hours
Message-Id: <9203280344 DOT AD10286 AT nwd2sun1 DOT analog DOT com>
To: <djgpp-request AT sun DOT soe DOT clarkson DOT edu>
 
   ----- Transcript of session follows -----
421 spd.analog.com: Host oceanus.spd.analog.com is down
 
   ----- Unsent message follows -----
Received: from adi.analog.com by nwd2sun1.analog.com (4.1/SMI-4.1)
 id AA09825; Fri, 27 Mar 92 18:58:04 EST
Received: from barnacle.erc.clarkson.edu by cs.umb.edu (5.65c/1.34)
 id AA07681; Fri, 27 Mar 1992 18:50:55 -0500
Received: from sun.soe.clarkson.edu by barnacle.erc.clarkson.edu with SMTP (PP)
          id <12874-0 AT barnacle DOT erc DOT clarkson DOT edu>;
          Fri, 27 Mar 1992 18:26:10 -0500
Received: by sun.soe.clarkson.edu (4.1/SMI-4.1) id AA15968;
          Fri, 27 Mar 92 17:23:06 EST
Return-Path: <ericb AT lsid DOT hp DOT com>
Received: from relay.hp.com by sun.soe.clarkson.edu (4.1/SMI-4.1) id AA15963;
          Fri, 27 Mar 92 17:22:57 EST
Received: from labejb.lsid.hp.com by relay.hp.com
          with SMTP (16.6/15.5+IOS 3.13) id AA10625;
          Fri, 27 Mar 92 14:20:42 -0800
Received: by labejb.lsid.hp.com (16.6/15.5+IOS 3.22) id AA17149;
          Fri, 27 Mar 92 14:20:37 -0800
From: Eric Backus <ericb AT lsid DOT hp DOT com>
Message-Id: <9203272220 DOT AA17149 AT labejb DOT lsid DOT hp DOT com>
Subject: Re: globbing and shells
To: 99clifto AT lab DOT cc DOT wmich DOT edu
Date: Fri, 27 Mar 92 14:20:35 PST
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
In-Reply-To: <9203271950 DOT AA18076 AT lab DOT cc DOT wmich DOT edu>; from "99clifto AT lab DOT cc DOT wmich.
edu" at Mar 27, 92 2:46 pm
Mailer: Elm [revision: 66.25]
 
> Assuming you wanted to distribute a program, the only drawback of
> adding the globbing routines to your program is the extra size
> overhead. In other words, if the shell expands wildcards then calls
> to glob produce nothing--all files are single strings in argv[?]...
> Of course you could also test for various shells and decide on a
> technique at run-time, but this introduces more overhead and
> complicates matters greatly.
>
> Why not create a library of routines that address the short comings
> of working in the dos environment, add a standard include file to
> prototype/define the routines and link to it at compile time?
 
If we modified crt0.o to add globbing, we wouldn't have to change the
source code of the application at all.
 
Furthermore, if we modified go32 to do globbing if a particular string
was found in the GO32 environment variable, we could turn globbing on
and off for an application at runtime by changing the GO32 environment
variable.
 
Either of these solution look good to me.  I can't work on go32 since
I don't have Borland cc, so maybe I'll look at modifying crt0.o.
--
    Eric Backus
    ericb%hplsla AT hplabs DOT hp DOT com
    (206) 335-2495

- Raw text -