Stef, Over the years I have seen all kinds of weird junk in mcz file names, including a number with embedded $(. Presumably that code was put in in self defense against a poorly formed file name in one of the repositories that Lukas was using:) Dale ----- Original Message ----- | From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> | To: Pharo-project@lists.gforge.inria.fr | Sent: Thursday, January 24, 2013 7:03:00 AM | Subject: Re: [Pharo-project] looking for the description of the MC file package format convention | | I found | | GoferVersionReference>>parseName: aString | | basicName | | basicName := aString last isDigit | ifTrue: [ aString ] | ifFalse: [ (aString copyUpToLast: $.) copyUpTo: $( ]. | package := basicName copyUpToLast: $-. | (package includes: $.) | ifFalse: [ branch := '' ] | ifTrue: [ | branch := package copyAfter: $.. | package := package copyUpTo: $. ]. | author := (basicName copyAfterLast: $-) copyUpToLast: $.. | versionNumber := (basicName copyAfterLast: $-) copyAfterLast: $.. | (versionNumber notEmpty and: [ versionNumber allSatisfy: [ :each | | each isDigit ] ]) | ifTrue: [ versionNumber := versionNumber asInteger ] | ifFalse: [ versionNumber := 0 ] | | Now I do not get why we have copyUpTo: $( | may be some files have ( ) | | Does anybody remember? | | Stef