From: Jonathan A R. <ja...@mu...> - 2004-05-20 15:31:23
|
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 |