Smalltalk › Frameworks & Tools › Monticello, Metacello ... › Metacello

Multiple dots in file names on git

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Sean P. DeNigris

Multiple dots in file names on git

Administrator

https://github.com/dalehenrich/metacello-work/tree/1.0-beta.31.1.5/repository/ConfigurationOfMetacello.package/ConfigurationOfMetacello.class/instance

Some of the method files have one dot (e.g. project.st), others have two (e.g. development..st). Why is that?

Cheers,
Sean

Frank Shearar-3

Re: Multiple dots in file names on git

On 14 July 2012 01:11, Sean P. DeNigris <[hidden email]> wrote:
> https://github.com/dalehenrich/metacello-work/tree/1.0-beta.31.1.5/repository/ConfigurationOfMetacello.package/ConfigurationOfMetacello.class/instance
>
> Some of the method files have one dot (e.g. project.st), others have two
> (e.g. development..st). Why is that?

FileTree munges names because some platforms dislike certain
characters in filenames. In particular, $: - > $., so a method called
#development: will go into a file called development. with extension
st, hence development..st. Array's #with:with: would thus go in a file
called with.with..st.

frank

Sean P. DeNigris

Re: Multiple dots in file names on git

Administrator

Frank Shearar-3 wrote

FileTree munges names because some platforms dislike certain
characters in filenames. In particular, $: - > $.

Do all trouble-causing characters transform to $. or is that just the mapping for $:? I think translating to e.g. http encoding would be more intention revealing. It was a little disconcerting to see the ".." and if all special chars are translated to $., there's a slight possibility for collisions e.g. an FFI function wrapper with an $_ where another has a $:

Cheers,
Sean

Cheers,
Sean

Frank Shearar-3

Re: Multiple dots in file names on git

On 14 July 2012 15:09, Sean P. DeNigris <[hidden email]> wrote:

>
> Frank Shearar-3 wrote
>>
>> FileTree munges names because some platforms dislike certain
>> characters in filenames. In particular, $: - > $.
>
> Do all trouble-causing characters transform to $. or is that just the
> mapping for $:? I think translating to e.g. http encoding would be more
> intention revealing. It was a little disconcerting to see the ".." and if
> all special chars are translated to $., there's a slight possibility for
> collisions e.g. an FFI function wrapper with an $_ where another has a $:

https://github.com/dalehenrich/filetree/blob/pharo1.3/repository/MonticelloFileTree-Core.package/MCFileTreeStCypressWriter.class/instance/fileNameForSelector..st
only maps $:. I'm pretty sure Dale wrote up the reasons for the name
mangling; I seem to recall HTTP encoding in that discussion. I can't
remember the conclusions/reasons though, sadly.

frank

> Cheers,
> Sean
>
> --
> View this message in context: http://forum.world.st/Multiple-dots-in-file-names-on-git-tp4639952p4640010.html
> Sent from the Metacello mailing list archive at Nabble.com.

Sean P. DeNigris

Re: Multiple dots in file names on git

Administrator

Frank Shearar-3 wrote

I can't remember the conclusions/reasons though, sadly.

There is an open issue at https://github.com/CampSmalltalk/Cypress/issues/9 which references the initial conversation. The argument (which I think is a good one) against http or similar encoding is to keep things human-readable, which I think is important, esp. for the outside world to look in and during our transition to git. $. just seems like a confusing substitution because it already has meaning in filenames, so the domains clash. I'd vote for $-, as Damien Pollet suggested.

Cheers,
Sean