[Jscheme-devel] Re: [Jscheme-user] Multiple Independent JSchemes (Timothy John Hickey)

[Timothy J. H. <ti...@cs...>]

How about renaming JS to be JScheme for the independent interpreters
and then reimplementing the old JS to use the single static instance of 
a JScheme
element as Jonathan suggests.  This would mean we would write code 
like...

> import "jscheme.JScheme";
>
> ...
> Jscheme js = new JScheme();
> System.out.println(js.call("java.util.Date."));

The JS class will be a deprecated class as Jonathan suggests.

---Tim---

On May 20, 2004, at 11:28 AM, Jonathan A Rees wrote:

> Although I'm definitely in favor of institutionalizing the ability to
> make instances of the interpreter, I'm also the sort of person who
> gets annoyed at unnecessary backwards incompatibilities.  May I
> suggest that you can have it both ways by keeping the static methods
> around, but have them use some distinguished instance, stored
> internally in a static field of some jsint class?  Then old code (like
> mine) can use new versions of the library without having to switch
> from the old static methods to the new dynamic ones, at least during a
> transition period.  The static methods can be marked 'deprecated', and
> clients can update their code at their leisure.
>
> Jonathan
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 
> 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Jscheme-user mailing list
> Jsc...@li...
> https://lists.sourceforge.net/lists/listinfo/jscheme-user