Xref: utzoo comp.lang.c:25322 comp.unix.questions:19334
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!samsung!uunet!mcsun!hp4nl!star.cs.vu.nl!maart
From: maart@cs.vu.nl (Maarten Litmaath)
Newsgroups: comp.lang.c,comp.unix.questions
Subject: Re: Unseting positional parmaters from inside a program
Message-ID: <5169@pinas.cs.vu.nl>
Date: 23 Jan 90 00:47:40 GMT
References: <481d9fde.14a1f@force.UUCP>
Reply-To: maart@cs.vu.nl (Maarten Litmaath)
Followup-To: comp.unix.questions
Organization: VU Informatika, Amsterdam, the Netherlands
Lines: 23

In article <481d9fde.14a1f@force.UUCP>,
	covertr@force.UUCP (Richard E. Covert) writes:
\...
\args=`./setargs "ab:" "avar:bvar" "$@" `
\...
\_______________ screen dump of test_setargs __________________
\args is avar=1;bvar='bs string';set -- 
\...

The problem:

	set --

doesn't unset the arguments (set $# to 0), it does nothing, which is a bug
(dubious feature) IMHO.  Solution:

	set x <the remaining arguments, if any>
	shift

Followups to comp.unix.questions.
-- 
  What do the following have in common:  access(2), SysV echo, O_NONDELAY?  |
  Maarten Litmaath @ VU Amsterdam:  maart@cs.vu.nl,  uunet!mcsun!botter!maart