[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Wrt to Tru64
From: |
Ossama Othman |
Subject: |
Re: Wrt to Tru64 |
Date: |
Mon, 23 Apr 2001 14:09:45 -0700 |
User-agent: |
Mutt/1.2.5i |
Hi Gary,
On Mon, Apr 23, 2001 at 10:06:23AM +0100, Gary V. Vaughan wrote:
>
> I think there is an underlying problem with the way output_verbose_link_cmds
> is not quoted prior to being `eval'ed. By my reckoning, it should be passed
> through $sed_quote_subst before being fed to eval, otherwise technically
> variables will also be substituted at the wrong time.
Right, that makes sense. It's strange that this problem is showing up
now. I recall testing that code successfully on Tru64 quite some time
ago.
> Additionally, it breaks our naming convention: *_cmds variables should allow
> multiple lines of shell code to be used if separated by `~'s; if a variable
> can hold only a single line of shell code, it should be name *_cmd.
Unless I'm missing something, I don't think that there is anything
preventing that variable from holding more than one line of code. It
just so happens that I used semi-colons instead of the tildes. Should
we switch to tildes instead?
-Ossama
--
Ossama Othman <address@hidden>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8