Regarding the PS, just because it possibly causes problems in one edge case is no reason to not make backports available to assist in making code run across multiple versions, to assist in porting, and to keep packages running on stable Julia. The benefits far outweigh the occasional cost, sorry you might have got hit with the cost.
Cheers Lex On Saturday, March 14, 2015 at 1:54:55 AM UTC+10, Avik Sengupta wrote: > > > So JavaCall has always had an "isnull(::JavaObject)" method, which is > exported. > > Now that Base has "Nullable" in v0.4, it also has an isnull(::Nullable) > method exported. > > So far so good. But I want to use Compat for JavaCall, primarily for the > Int/int change. Now, Compat also has an isnull(::Nullable) method exported, > but that is in the module Compat! > > So I cant figure out how to write the definition of "isnull" in JavaCall, > that'll work in all versions of Julia. > > Any help appreciated. > > Regards > - > Avik > > PS> Maybe this is another reason why new functionality should NOT be > backported, even in compat? >
