2014-04-08 19:04 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:
Argh, yeah, another namespace problem. Sorry you had to run into that.
Don't sorry. It was just a matter of trying to load it.
I do wonder though: is there no warning when you are (about to) overwrite an existing class ?
Apparently not :D
And I would never name any class of mine anything general like Cache or Record without a namespace prefix.
The main code trunk is in VisualWorks, which uses namespaces extensively. So migrating to Pharo/Squeak with an added prefix is not an option, or requires a lot of rewrites during the fileout.
There should indeed be a CI job, I thought there was talk about a DBX one, but I can't find it.
I haven't seen it either.
From my standpoint GLORP is abandoned in the Pharo realm. There are some people, like me, that still use it, but no one maintains it. It worries me that not a single person ran into this issue before, during the whole testing of Pharo 3. Well... I am now, but I'd expect more people using GLORP.
Esteban A. Maringolo