Re: [ease-dev] Script shell prints [null] on no result

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

My minimal suggestion is for the display only, i.e. no change to
contents of ScriptResult. We still store null in there because at that
point it is in Java land.

I'll update the earlier gerrit with an idea.

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 18 May 2016 at 21:33, Christian Pontesegger
<christian.pontesegger@xxxxxx> wrote:
> Javascript is even more annoying
>
> a = 1
>      1.0
> var b = 1
>     [null]
>
> So the 'var' keyword changes behavior here. I see that in some cases it
> would make sense to return the 'null' representation of the target language
> like you described in your post. For that we could avoid transforming the
> PyNone object to 'null' when we convert it to the java world. Possibly this
> is an option. However when your script returns something (eg to another
> script, to a shared storage, etc) you do want to have script language
> independent artifacts. PyNone would be of no use to anything else than
> Jython. Even another python interpreter would be lost with that specific
> object.
>
> Also 'null' could be used as an input value for a Java method - and might
> make sense in some cases. PyNone would be problematic here.
>
> So I see use cases for both ways of implementation. Personally I am not sure
> which one is better. Having preferences for that is also not very promising
> as different installations of EASE might get incompatible to each other.
>
> I do see your point here but cannot think of a clean implementation so far.
> We have to decide for one way or the other, both have benefits and drawbacks
> depending on your use case.
>
> Christian
>
> _______________________________________________
> ease-dev mailing list
> ease-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/ease-dev