zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: PATCH: function copy
Date: Tue, 16 Jul 2019 12:11:17 -0700	[thread overview]
Message-ID: <CAH+w=7ZD88T5bHXGJebsaa0CNv8NezDGLxjB7Xop3UcWmQ=R7A@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7YiA6zHgwGPYFFgLng_pjtOZtGc9BHCFAoOZMLmtGFJyA@mail.gmail.com>

One other thought ...

On Tue, Jul 16, 2019 at 12:06 PM Bart Schaefer
<schaefer@brasslantern.com> wrote:
>
> On Tue, Jul 16, 2019 at 1:56 AM Peter Stephenson
> <p.stephenson@samsung.com> wrote:
> >
> > On Mon, 2019-07-15 at 14:42 -0700, Bart Schaefer wrote:
> >
> > > "around" you need a way to say "call the original function HERE"
> >
> > I think you're implying you'd rather not have an additional function
>
> There doesn't need to be any special syntax, just some special name
> linking

The other significant thing about "not have an additional function" is
that ideally _my_fn and _orig_fn would occur at the same locallevel,
that is, the call to the original function would not push a new
parameter context onto the stack but would instead behave as if you'd
eval'd the source text of the advised function.

  reply	other threads:[~2019-07-16 19:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 20:00 Peter Stephenson
2019-07-15 20:23 ` Sebastian Gniazdowski
2019-07-15 21:25   ` Peter Stephenson
2019-07-15 21:42 ` Bart Schaefer
2019-07-15 21:51   ` Sebastian Gniazdowski
2019-07-15 22:08     ` Bart Schaefer
2019-07-16  8:56   ` Peter Stephenson
2019-07-16 16:55     ` Philippe Troin
2019-07-16 19:06     ` Bart Schaefer
2019-07-16 19:11       ` Bart Schaefer [this message]
2019-08-03 18:58 ` Peter Stephenson

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='CAH+w=7ZD88T5bHXGJebsaa0CNv8NezDGLxjB7Xop3UcWmQ=R7A@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /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).