Geert,
good points. The next question is then, why not make "atTopPriority"
the default one? Wouldn't that make everybody happy through a single
method API? Is it needed to be able to add at the bottom?
So, what about:
- keep the actual three addResourceBundle(s) without atTopPriority
argument: by default the added bundle(s) will be put in top priority,
- when bottom priority needed, then the caller retrieves the list itself
with getResources, and works directly on the list.
Regards
Pierre
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
