cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dev at weitling <>
Subject Re: RT: map:call as generic non-redirecting controller code
Date Fri, 06 Jul 2007 10:50:13 GMT

Grzegorz Kossakowski wrote:
> Dev at weitling pisze:
>> To be able to put a function call anywhere in a pipeline would be great,
>> having access to all the variables defined up till then. To return data
>> to the pipeline for further processing via a special protocol doesn't
>> look like the best way to go (IMO). Functions should only return (in the
>> classical way) data to other functions calling them.
> Florian, I'm not sure if I understand you correctly. What's the use to
> return data from function call if you can't process it later?

I'm not against processing data, I want to avoid introducing a new
protocol. And functions returning values the classical way (return
myBestStuff;) will reduce readability of the pipeline. For few and/or
small values I'd prefer variables, for many and/or big values one should
think about introduce a generator or transformer weaving the data
directly into the pipeline.
Giving even void functions a sense: Doing something when a certain point
in a pipeline is reached not directly touching data flowing through the

Hope this was not even more obfuscating :-)

View raw message