zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: limit scope of variable
Date: Tue, 3 Aug 2021 13:39:28 -0700	[thread overview]
Message-ID: <CAH+w=7a5k9-Eg44z8zyE7zcdYzMGKWHipg2s5ca7pcVAAh1-Eg@mail.gmail.com> (raw)
In-Reply-To: <bd1be7c6-1bcd-c762-9add-031abc1744c5@eastlink.ca>

On Tue, Aug 3, 2021 at 1:15 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> I have a function that requires this:
>
>      local IFS=$'\n'
>
> ... but the function calls other functions in which I need to protect
> $IFS from that change.  Can I limit the scope?

That's what the zsh/param/private module is for, but unfortunately,
because IFS is a special parameter, you can't declare it private.

You can, however, declare IFS local in both functions, to avoid having
to explicitly restore it in the "inner" function.

calling_function() {
  local OLDIFS=$IFS
  local IFS=$'\n'
  called_function
}
called_function() {
  local IFS=$OLDIFS
  ...
}

However, it seems odd to me that called_function cares about the
$OLDIFS value.  I would think it either does not care, or needs to
declare its own value explicitly.  That is, I would think you don't
need $OLDIFS, and instead can do something like

called_function() {
  local IFS; unset IFS # use default
  ...
}


  reply	other threads:[~2021-08-03 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 20:15 Ray Andrews
2021-08-03 20:39 ` Bart Schaefer [this message]
2021-08-04  0:09   ` Ray Andrews
2021-08-03 20:41 ` Vin Shelton
2021-08-03 20:44   ` 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='CAH+w=7a5k9-Eg44z8zyE7zcdYzMGKWHipg2s5ca7pcVAAh1-Eg@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=rayandrews@eastlink.ca \
    --cc=zsh-users@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).