My general feeling: anytime we make something "public" it becomes "set in stone". So, it is best not to make things public ahead of clear needs/use-cases. That way, if at some point in the future, we find we now have a clear use-case for the loadBinary kind of thing, we can implement it then, without any worries about backwards compatibility :-).
Kind of a "lazy" API creation, I guess. -Marshall On 8/3/2016 12:12 PM, Peter Klügl wrote: > We can make them private, but I thought that maybe someone want to > directly load a binary cas. Well that's not really necessary. > > > Best, > > > Peter > > > Am 03.08.2016 um 18:10 schrieb Marshall Schor: >> This class is a collection of static methods, mostly variants of "load" and >> "save". >> >> There are 3 public methods "loadBinary" that appear to be called from various >> "load" methods. >> >> Could these loadBinary methods be changed to private, instead of public, or >> do >> they need to be part of the public API? >> >> -Marshall >
