2017-11-10 16:21 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
On 10 Nov 2017, at 16:11, Nicolas Cellier <nicolas.cellier.aka.nice@ gmail.com> wrote:
There are other possibilities: if we don't want to change the methodBody at all, then let's change the opening/closing sequence
- at write, choose a closing sequence that has no exact match in source code, then use the inverse sequence as the opening sequence - at read, just scan for the inverse of opening sequence
opening sequence could be any combination of [{<( or maybe just a single [ repeated as many times as necessary
That is a cool idea (used by some scripting languages, stdin handling, IIRC).
Check for conflicts of 1 $] closing sequence for $[ and keep on increasing the count until there is no conflict. Simple & effective. Supports any syntax.
BTW, I held off from commenting about the basic Tonel principle of a single file, but if 'we want to allow people to edit this file manually' becomes a goal, then I would be VERY VERY disappointed.
Sven
Bah, pragmatism rules, for patching a typo directly thru github API, it's
OK... If it's about replacing IDE with vi, then it's no more Pharo.