Hello there,
I have just seen the changes you want to apply to java.util.Locale in
JDK 8 and was wondering why you are forcing the use of a java.util.List
in the lookup and filter methods. The related methods of
java.util.Locale are
public static Locale lookup(List priorityList,
Collection
(adding core-libs-dev)
Hi Christian,
RFC 4647 defines The Language Priority List [1]. The use of
java.util.List would be a natural fit, which is the reason why List is
used. But use of Iterable does work (as API design). The parameter name
`priorityIterable' sounds a bit odd, though.
Does u
- Original Message -
> On 08/27/2013 03:00 AM, Masayoshi Okutsu wrote:
> > /etc/sysconfig/clock used to be supported, but it was removed in JDK 7.
> > The problem is discussed in bug #6456628.
> >
> > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6456628
>
> Thanks for that link. I d
Hey,
I haven't digged so deep where java.util.List is used but thanks for the
pointer.
I have no problem with the usage of java.util.List as stated before. I
am just thinking that, if someone for example uses a java.util.Set to
represent the priorities, it would be necessary to construct a Lis
On 28/08/2013 14:25, Masayoshi Okutsu wrote:
(adding core-libs-dev)
Hi Christian,
RFC 4647 defines The Language Priority List [1]. The use of
java.util.List would be a natural fit, which is the reason why List is
used. But use of Iterable does work (as API design). The parameter
name `priori
