From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: was: Re: endianness of wordcode
Date: Fri, 31 Mar 2000 09:06:04 +0200 (MET DST) [thread overview]
Message-ID: <200003310706.JAA07712@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Thu, 30 Mar 2000 15:57:42 +0000
Bart Schaefer wrote:
> On Mar 30, 12:56pm, Sven Wischnowsky wrote:
> } Subject: Re: PATCH: was: Re: endianness of wordcode
> }
> }
> } Bart Schaefer wrote:
> }
> } > On Mar 29, 11:14am, Sven Wischnowsky wrote:
> } > } Subject: Re: PATCH: was: Re: endianness of wordcode
> } > }
> } > } So, this adds the -a option to zcompile which is needed to make
> } > } functions that are currently only marked for autoloading to be written
> } >
> } > This is still a bit odd, because it means you have to check yourself
> } > whether a function is defined or undefined before you know what result
> } > "zcompile -a -c ..." is going to produce. I'd rather that you simply
> } > CAN'T compile both defined and undefined functions in the same pass.
> }
> } Hm. Consider someone who has all his functions autoloaded (i.e. none
> } defined in .zshrc or other init files) and doesn't use kshautoload.
> } With the current state he can do `zcompile -ca all-funcs' to write them
> } all into one file. If we disallow compiling both already-loaded and
> } not-yet-loaded functions `in the same pass', it is impossible to do
> } that if at least one of the functions happens to be loaded already.
>
> But that user will still get the wrong result if e.g. _cvs is one of the
> functions that happens to be loaded already. Isn't it better to have to
> expend slightly more effort to get consistent and correct results than to
> easily be able produce an inconsistent and sometimes incorrect results?
>
> Even something as simple as searching $fpath and printing a warning when
> a file with the same name as an already-loaded function is found, would
> be preferable to silently doing the wrong thing. (That warning would be
> printed only when -a is given, of course.)
I'm starting to give in...
So, make `-a' the opposite of not-`-a', i.e. barf when there are
names of function not still makred for autoloading. Yes?
Or maybe make `-a' the opposite of `-c'? I.e. `-c' says that currently
defined (not marked for autoloading) functions are to be written and
`-a' says functions marked for autoloading are to be written. We could
then say `...to be written without signalling an error', so that `-ca'
allows to mix both (I think I really want a way to do that, but it's
ok for me to make it as far from the default as possible). And then we
can add a description of the _cvs problem in the manual, so that
people know why using this might be a problem.
Would that be acceptable for everyone?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-03-31 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-31 7:06 Sven Wischnowsky [this message]
2000-03-31 12:34 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-03-31 13:00 Sven Wischnowsky
2000-03-31 16:56 ` Bart Schaefer
2000-03-30 10:56 Sven Wischnowsky
2000-03-30 15:57 ` Bart Schaefer
2000-03-29 9:14 Sven Wischnowsky
2000-03-29 17:40 ` Bart Schaefer
2000-03-28 12:32 Sven Wischnowsky
2000-03-28 18:04 ` Bart Schaefer
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=200003310706.JAA07712@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).