From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: rc@archone.tamu.edu
Subject: Re: export of variables and functions
Date: Fri, 27 Sep 1991 11:04:41 -0500 [thread overview]
Message-ID: <91Sep27.120446edt.2706@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: malte's message of Fri, 27 Sep 91 06:02:05 -0400. <9109271002.AA07020@dahlie.techfak.uni-bielefeld.de>
I actually think that exporting everything is the right decision,
and certainly should be the default. All of my 'local' variables
tend to be function-local, as opposed to shell-local, and we already
have a mechanism for that. How many shell-local variables do people
have/would have?
- cks
next prev parent reply other threads:[~1991-09-27 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-09-27 10:02 malte
1991-09-27 16:04 ` Chris Siebenmann [this message]
1991-09-27 13:29 Rich Salz
1991-09-27 14:24 Donn Cave
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=91Sep27.120446edt.2706@hawkwind.utcs.toronto.edu \
--to=cks@hawkwind.utcs.toronto.edu \
--cc=rc@archone.tamu.edu \
/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.
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).