From: Tim Goodwin <tjg@star.le.ac.uk>
To: carlos@texne.com
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: environment again
Date: Mon, 12 Jun 2000 11:23:55 -0400 [thread overview]
Message-ID: <4AcAAKEARTmN4wYA@ltsun0.star.le.ac.uk> (raw)
In-Reply-To: <E1307Zs-0001R0-00@localhost>
> { Col1='data1'; Col2='data2'; Col3='some-big-data' }
> [...]
> sed 's/__SPECIAL_TAG__/'^$Col3'/' page_template.html
What's the problem with simply doing this? Is Col3 so enormous that
you're running into environment variable limits? Or are you worried
about performance?
If it's performance, "profile, don't speculate!" It would be very
interesting to see some test results showing just how much it costs to
have some enormous variables in the environment.
Finally, if I've understood correctly what you're trying to achieve,
there is a workaround, although it's rather ugly.
eval 'Col3=() sed s/__SPECIAL_TAG__/'^$Col3^'/ page_template.html'
Tim.
next prev parent reply other threads:[~2000-06-13 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 19:02 Carlo Strozzi
2000-06-12 15:23 ` Tim Goodwin [this message]
2000-06-12 16:35 ` Carlo Strozzi
-- strict thread matches above, loose matches on Subject: below --
2000-06-08 7:19 Carlo Strozzi
2000-06-08 16:48 ` Decklin Foster
2000-06-07 6:53 Carlo Strozzi
2000-06-08 5:55 ` Decklin Foster
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=4AcAAKEARTmN4wYA@ltsun0.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--cc=carlos@texne.com \
--cc=rc@hawkwind.utcs.toronto.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).