GemTalk / Sparkle

MIT License
11 stars 5 forks source link

Pharo and Rowan tonel writers write definitions in different formats #11

Closed dalehenrich closed 3 years ago

dalehenrich commented 3 years ago

Rowan can read Pharo tonel format and Pharo can read Rowan tonel format, but there are non-sematic differences in the file formats that leads to spurious code differences when comparing source.

If it becomes a big enough problem, we might be able to patch the Pharo9 tonel writer to conform to the format used by Rowan in order to avoid a lot of diff noise.

In the long run Rowan needs to be able to write using the pharo format (impying that there will be a different tonel format that needs to be supported), but in the short term a relatively simple tonel hack would be more expedient

martinmcclure commented 3 years ago

RSR patches Pharo to output the symbol->string format. Are there other problems in writing Sparkle code from Pharo?

dalehenrich commented 3 years ago

If this is patched, then we are good to go ... this was a preemptive bug report, because I anticipated problems :)