help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: Suggestions for autogenerating function names to wrap the same code?
Date: Tue, 22 Mar 2022 21:03:32 +0000	[thread overview]
Message-ID: <c9a0dbe3dd4234c398150c476eef3284ce978067.camel@ntlworld.com> (raw)
In-Reply-To: <38A2973E-E198-4E15-8DCF-C4C72EBC2B58@dondley.com>

On Tue, 2022-03-22 at 16:52 -0400, Steve Dondley wrote:
> So I have these two functions:
> function task() {
>     task_wrapper.pl $funcstack[1] "$@"
> }
> function tc() {
>     task_wrapper.pl $funcstack[1] "$@“
> }
> They are both wrappers for the same perl script which does its thing
> based on the value of $funcstack[1]; 
> Works, but I’m wondering if I can spare myself the job remembering to
> create a new function for each and every new perl function I want to
> write.
> I could write a little script to pull out the subroutine names from
> the perl script and dump them into a file sourced by zsh and then reload
> zsh.
> Wondering if there might be some cool feature of zsh I don’t know
> about to assist with creating these functions on-the-fly.

Recent versions of the shell allow you to copy functions from an old
name to a new name.  It's efficiently implemented internally.

% oldname() { print I am $0: }
% oldname
I am oldname
% functions -c oldname newname
% newname
I am newname


  reply	other threads:[~2022-03-22 21:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 20:52 Steve Dondley
2022-03-22 21:03 ` Peter Stephenson [this message]
2022-03-22 21:03 ` Mikael Magnusson
2022-03-22 21:09   ` Steve Dondley
2022-03-22 23:37     ` Steve Dondley
2022-03-22 21:16   ` Bart Schaefer
2022-03-22 23:28   ` Steve Dondley
2022-03-22 23:44     ` Steve Dondley

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:

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

  git send-email \
    --in-reply-to=c9a0dbe3dd4234c398150c476eef3284ce978067.camel@ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@zsh.org \


* 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


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).