Re: argument parser throws error if 0-length $args used...
- From: "Alex K. Angelopoulos \(MVP\)" <spam.aka.maps@xxxxxxxx>
- Date: Sun, 11 Sep 2005 13:04:19 -0500
Er - they CAN be space-delimited. They work with commas too, if you use ()
around the argument list. :)
"Ryan Milligan" wrote in message news:P_qdnSGYoJIYWL7eRVn-3w@xxxxxxxxxxxxxx
> Heh...I knew I had to be missing something. Arguments to functions are
> space-delimited, not comma-delimited, just like normal commands. My
> apologies. I plead seventy hour weeks plus weekends spent at work.
.
- Follow-Ups:
- Re: argument parser throws error if 0-length $args used...
- From: Ryan Milligan
- Re: argument parser throws error if 0-length $args used...
- References:
- MSH: argument parser throws error if 0-length $args used...
- From: Alex K. Angelopoulos \(MVP\)
- Re: argument parser throws error if 0-length $args used...
- From: Jon Newman [MSFT]
- Re: argument parser throws error if 0-length $args used...
- From: Jeffrey Snover
- Re: argument parser throws error if 0-length $args used...
- From: Alex K. Angelopoulos \(MVP\)
- Re: argument parser throws error if 0-length $args used...
- From: Jeffrey Snover
- Re: argument parser throws error if 0-length $args used...
- From: Ryan Milligan
- Re: argument parser throws error if 0-length $args used...
- From: Jeff Jones [MSFT]
- Re: argument parser throws error if 0-length $args used...
- From: Ryan Milligan
- Re: argument parser throws error if 0-length $args used...
- From: Ryan Milligan
- MSH: argument parser throws error if 0-length $args used...
- Prev by Date: Re: Process block in a filter is not a new scope - is this right?
- Next by Date: MSH: Accessing ADSI interfaces and Q on WinNT Provider
- Previous by thread: Re: argument parser throws error if 0-length $args used...
- Next by thread: Re: argument parser throws error if 0-length $args used...
- Index(es):
Relevant Pages
|
