cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: Polishing the flow contracts
Date Mon, 31 Mar 2003 08:59:13 GMT
Jakob Praher wrote:
> Am Son, 2003-03-30 um 21.32 schrieb Stefano Mazzocchi:
> 
> 
> 
>>>>4) the following functions
>>>>
>>>>Flow Object:
>>>>  flow.import() -> imports another flowscript
>>>
> 
>> 
>>
>>>Hmmm... Should we allow cross-language (when/if we're going to have it)
>>>flowscripts interaction? Because otherwise I'd prefer a name such as
>>>"interpreter"....
>>
>>I don't get it. What's wrong with the name flow?
>>
> 
> 
> I think the same as Pier here, you merely don't include a flow, but
> include or import another javascript file. Using flow here, I think,
> leads the user to false assumption, that this is flow specific.
> For instance using jruby or another great scripting language (jython,
> ...), this would work somewhat different like Module::include in jruby
> or import in jython.

Ok, I agree with you people.

I wonder, doesn't javascript have such a native facility for importing 
external scripts? I would be surprised if it didn't.

Chris? (you are the javascript guru around here :)

Stefano.



Mime
View raw message