Yes +1 to that idea, I've had the same problem For backwards compatibility we could keep the overloads with the String typed lang argument and just mark those methods as deprecated to gently prod people to move to the newer overloads
Rob On 7/16/12 11:02 AM, "Ian Dickinson" <[email protected]> wrote: >Andy - >This all sounds good to me. Would it be possible to use a different Java >type than string for the lang? Just to avoid the confusion that I >*still* suffer from in remembering which order the arguments go in >Model.read( String, String, String ) > >Ian >
