RE: An unfulfilled requirement maybe?

Oh. That. Well, again, if a sysntax for environmental variables is
established, an explicit reference to the PATH may be added in the command
path and/or CWD. Suppose AVTs were the type of syntax, then the final path
may be something like:
<p:exec ... command="{PATH}perl" ... />


Another way, now that I think about it, could possibly involve a new
extension function (suppose called something like p:env($varname as string))
that can be embedded in one of the options like:

<p:exec>
<p:option name="command" select="concat(p:env('PATH'),'perl')"/>
</p:exec>

In this case, CWD is of no importance, since PATH is always an absolute path
(or at least is by default anyway).
-----Original Message-----
From: Henry S. Thompson [mailto:ht@inf.ed.ac.uk] 
Sent: Tuesday, November 27, 2007 9:21 PM
To: Vasil Rangelov
Cc: public-xml-processing-model-comments@w3.org
Subject: Re: An unfulfilled requirement maybe?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vasil Rangelov writes:

> "search path"? What is that? That's the first time I hear about it, and I
> found no info on Wikipedia about it.

The PATH environment variable.  On your proposal, how can I write a
pipeline which e.g. runs perl w/o knowing the full path to its
location?

As things stand, I just say <p:exec . . . command="perl". . ./>, but
that won't work under your proposal.

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged
spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFHTG4MkjnJixAXWBoRAsOfAJ9VAj+WEjrf4DOZjaUJe8V4eXoDuwCdFgyO
Ni0hMMkkfct8qCfLDed390Y=
=MhoU
-----END PGP SIGNATURE-----

Received on Tuesday, 27 November 2007 19:41:03 UTC