On 16/07/12 19:11, Rob Vesse wrote:
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
Yes and no.
There is a "Lang" class - in RIOT currently it's an enum - it will be a
plain class to make it open ended can't add an case to an enum without
recompiling). c.f. ARQ's Symbol.
If we add model.read(X, base, Lang) the null case is a compile problem
and needs the null to be cast. Bother.
And if it's Object and introspection, it does not help the original case
of (X, String, String) much. Bother^2.
So how much is model.read(X, base, null) used? Not much I guess but do
changes mess up class/method signatures?
WebReader.readSomething(...) only takes Lang, not a string for there
hint. String hints exist and remain in Model.read only (and old
FileManager)
Andy
