zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Cc: 175467@bugs.debian.org
Subject: Re: zsh -n and modules
Date: Sun, 5 Jan 2003 22:35:31 +0000	[thread overview]
Message-ID: <1030105223531.ZM4130@candle.brasslantern.com> (raw)
In-Reply-To: <20030105201312.GA2058@dman.com>

On Jan 5,  3:13pm, Clint Adams wrote:
}
} If you run zsh -n on a script which uses zsh/mathfunc, zsh will
} not exec zmodload, and thus not be aware of new math syntax.

} Is an EXEC_ZMODLOAD option in order?

That solution is not particularly useful.  Consider something of the form

    if test ...
    then zmodload zsh/mathfunc
    fi

If you can't execute the conditional because of -n, how do you know that
it's safe to execute the zmodload?

IMO you've identified a deeper problem, which is that no module should be
allowed to alter the syntax accepted by the parser.  Conversely, if the
parser is able to cope with the syntax in the absence of the module, then
`zsh -n' has no business complaining about the semantics.

In this example:

> /usr/bin/vux:766: unknown function: int

`zsh -n' should simply accept that `int' IS a function, and should not try
to look it up.

In this case:

> /usr/bin/vux:784: bad math expression: operator expected at `h'

I can't give an opinion, "bad math expression" is too generic an error.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2003-01-05 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 20:13 Clint Adams
2003-01-05 22:35 ` Bart Schaefer [this message]
2003-01-06  0:19   ` Clint Adams
2003-01-06  2:02     ` Bart Schaefer
2004-03-11 16:31       ` Clint Adams
2004-03-14 16:24         ` Peter Stephenson
2004-03-14 18:17           ` Clint Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1030105223531.ZM4130@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=175467@bugs.debian.org \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).