Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!nsc!pyramid!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Pipes
Message-ID: <12396@cbmvax.commodore.com>
Date: 7 Jun 90 19:15:46 GMT
References: <2533@zipeecs.umich.edu> <136735@sun.Eng.Sun.COM> <1990Jun6.104643.15176@zorch.SF-Bay.ORG> <5aBo02FSad0201@amdahl.uts.amdahl.com>
Reply-To: jesup@cbmvax (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 24

In article <5aBo02FSad0201@amdahl.uts.amdahl.com> kim@uts.amdahl.com (Kim DeVaughn) writes:
>One related question I've asked several times, but still have not seen an
>answer to ... under 2.0, can command lines longer than ~255 chars be passed
>to Exec() ... or must file handling programs still be "builtin" to a shell, or
>do their own wildcard expansion if not, in order to handle directories with
>moderately a large number of files in it?  Could someone at CBM who knows,
>please comment?  Andy?  Randell?

	Command lines should be able to be longer as used by System and
Execute.  This hasn't been extensively tested as of yet, but it was a
factor in design.  Path lengths are still constrained by the 255 character
limit to BSTRs, due to the packet formats.  At some later date I have plans
to eliminate that as well (no time for 2.0).

	The console may be able to handle longer than 255 character lines
now, I'm not sure (but I suspect it still has some hard limit).

	Wildcard expansion is much easier to do now, due to matchfirst/
matchnext.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"