On 04 Jan 2014, at 14:38, Sven Van Caekenberghe <[email protected]> wrote:
> > On 04 Jan 2014, at 14:22, Sebastian Sastre <[email protected]> > wrote: > >> Thanks for the tip. >> >> AFAIK, STON would be best suited for JSON friendly instances. >> >> I need something more general. > > STON can work with most normal objects and is easy to customise or adapt. > >> What I was trying to do with sixx is to dump the airflowing odb's to migrate >> data so pharo 3 can use it.* The object databases are composed by many >> kinds of objects, only a few of them are JSON-ish > > I don’t know what you mean by JSON friendly objects, can you give an example > of something that you need that is not of that kind ? > >> PD: All this is due to the change that happened in DateAndTime #jdn -> >> #julianDayNumber which is forcing me to either abandon Pharo 3, do horrible >> hacks to it or stay with older pharo. > > OK, that is a rename, why can’t you just add it back ? and, you can not ask at the same time for “nice” APIs and then complain when we do what you ask… Marcus
