Re: command line variable assignments

[Aharon Robbins]

Gawk 3.1.0 was released over a year ago. The bug you're reporting
has long been fixed.

The current version is 3.1.1, released about two weeks ago.

Arnold

> Date: Thu, 16 May 2002 02:06:32 -0700 (PDT)
> From: Tom Lord <address@hidden>
> To: address@hidden
> Subject: command line variable assignments
>
> Versions 3.0.3 and 3.0.6 both seem to think that an "=" in a 
> command line argument indicates a variable assignment rather
> than a filename.  As I read the spec, this is so only if the 
> text to the left of the "=" begins with an underscore or letter and
> contains only characters which are valid in identifiers -- otherwise
> the argument must be treated as a filename.
>
> In other words:
>
>       ./gawk [....] /foo/bar/=dir/etc
>
> is not a syntax error or bad variable assignment -- it tells awk to
> read its input from the named file.
>
> The problem seems to be caused by calling `main.c(arg_assign)' in
> `io.c(nextfile)'.  `arg_assign' applies a check suitable for `-v'
> option arguments, but not for ordinary arguments.
>
> -t