Re: [Pharo-dev] Grease conflicts #packages with RPackage
Is there a pharo bug entry for this? It currently exists in Moose 5.0 (on Pharo 3.0) https://code.google.com/p/moose-technology/issues/detail?id=1018
On 02 Dec 2013, at 18:25, Stephan Eggermont <stephan@stack.nl> wrote:
Is there a pharo bug entry for this?
It currently exists in Moose 5.0 (on Pharo 3.0) https://code.google.com/p/moose-technology/issues/detail?id=1018
I have never seen this happening in Pharo. It seems it is more grease related. Marcus
Guys Do you think that if an external library redefines the semantics of #class, it will be a Pharo bug? The solution is ***REALLY*** simple, rename packages into grPackages and you are done.
From the Pharo core perspective we cannot do anything. We are sorry but yes we introduced packages, package because it was needed.
Stef
Is there a pharo bug entry for this?
It currently exists in Moose 5.0 (on Pharo 3.0) https://code.google.com/p/moose-technology/issues/detail?id=1018
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
participants (3)
-
Marcus Denker -
Stephan Eggermont -
Stéphane Ducasse