Filtering doesn't help if the package was saved from a Squeak or GemStone image or someone hand edited their package name ... I know that a number of folks don't care about anyone that isn't using the latest version of Pharo, but that is not the case for all developers. Monticello could be a common interchange format for code, but if folks impose incompatible restrictions on package names then we might as well give up on that possibility ... If you want to have a common interchange format, then you need to avoid unilateral changes that cause incompatabilites ... If you don't want to make common code more difficult than it needs to be, then you are headed down the right path ... I apologize in advance for offending anyone and I'll just shut up on this particular issue... Dale On 01/24/2011 02:20 PM, Miguel Cobá wrote:
Then an quick/easy fix is to filter out $. from the FullName prompt in the image.
Cheers
El lun, 24-01-2011 a las 14:16 -0800, Lukas Renggli escribió:
However, that doesn't change that $. and $- cannot be part of the PackageName or Author.
Just $., forget what I said about $-.
Lukas