W3C home > Mailing lists > Public > xproc-dev@w3.org > February 2012

RE: p:pipeline should make a closure over in-scope variables

From: Geert Josten <geert.josten@dayon.nl>
Date: Mon, 13 Feb 2012 13:13:37 +0100
Message-ID: <20c381fb6127014cbe586de869b5cdd7@mail.gmail.com>
To: Florent Georges <fgeorges@fgeorges.org>, vojtech.toman@emc.com
Cc: xproc-dev@w3.org
That's not possible? *surprised look*

I was sure I used it in my ebook code. But after looking at my code, I see
I am passing all kinds of configs through as params. (I have some generic
mechanism to do so, which saves me from having to make a distinction
between vars with defaults, params, and options that are actually kind of
used for the same purpose: passing through configs from 'outside' the app)

Grtz

> -----Oorspronkelijk bericht-----
> Van: fgeorges@gmail.com [mailto:fgeorges@gmail.com] Namens Florent
> Georges
> Verzonden: vrijdag 27 januari 2012 11:16
> Aan: vojtech.toman@emc.com
> CC: xproc-dev@w3.org
> Onderwerp: Re: p:pipeline should make a closure over in-scope variables
>
> On 11 January 2012 09:16, ? wrote:
>
> > Ideally, also the following should be supported to allow for
> > "global" variables:
>
> > <p:library>
> >  <p:variable name="base.dir" select="..." />
> >
> >  <p:pipeline>
> >    <!-- $base.dir should be available here -->
>
>   +1.  That's something I missed several times in the real life...
>
> --
> Florent Georges
> http://fgeorges.org/
> http://h2oconsulting.be/
Received on Monday, 13 February 2012 12:14:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 13 February 2012 12:14:04 GMT