Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site talcott.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!genrad!panda!talcott!lotto
From: lotto@talcott.UUCP (Jerry Lotto)
Newsgroups: net.micro.pc,net.micro
Subject: Re: null as variable in batch file
Message-ID: <565@talcott.UUCP>
Date: Tue, 11-Feb-86 08:55:49 EST
Article-I.D.: talcott.565
Posted: Tue Feb 11 08:55:49 1986
Date-Received: Wed, 12-Feb-86 21:39:38 EST
References: <534@whuts.UUCP>
Distribution: net
Organization: Harvard Univ. Chem. Dept.
Lines: 19
Xref: watmath net.micro.pc:6918 net.micro:13769
Summary: small correction to last posting

In article <534@whuts.UUCP>, 2212msr@whuts.UUCP (ROBIN) writes:
> Does anyone know how to detect a null as variable input in a batch file?
                                   ****
> Specifically:
> 
> foo %1   --how do I detect case where %1 is omitted, thus avoiding
                                              ********

	What do you really want to do here?  If you want to detect
no args, see the previous posting.  If you want to pass a null (ascii 0)
on a command line past the command processor, forget it.  The command
line parser will not respect your wishes.
-- 

Gerald Lotto - Harvard Chemistry Dept.

 UUCP:  {seismo,harpo,ihnp4,linus,allegra,ut-sally}!harvard!lhasa!lotto
 ARPA:  lotto@harvard.EDU
 CSNET: lotto%harvard@csnet-relay