Xython - XML-Formed Python

[Steve Horne]

On Mon, 4 Feb 2002 07:25:00 -0600, "Chris Gonnerman"
<chris.gonnerman at newcenturycomputers.net> wrote:

>----- Original Message ----- 
>From: "Steve Horne" <steve at lurking.demon.co.uk>
>
>[[ hack hack hack ]]
>
>> One major advantage is the possibility that source code could be more
>> concerned with semantics, and the presentation could be an issue for
>> the editor. No more arguments about indentation against braces - tell
>> the dissenters to simply configure their editor to work with braces
>> instead of (or as well as) indentation. With a sufficiently
>> sophisticated editor, the syntax of the language becomes 'skinnable'.
>
>Heaven help the poor fool who has to work at someone else's station or 
>on someone else's account...  would be MUCH worse than just a difference
>in coding style.

Nah - just keep everyones editor configuration files in a shared area.

The whole point is that you always see the code formatted in your
preferred style, irrespective of who wrote it - the stylistic
differences are separated from the source code, so that when you load
up someone elses source code into your editor, it is automatically
formatted the way you prefer it.

You can play any MP3 file irrespective of the skin you set up for the
player. The music is independent of the user interface. There are also
skinnable music editors. Just because the waveform display is a
different colour, or uses a spectral format, or is scaled differently
or whatever, that doesn't affect what music you can edit or what it
will sound like.

So who cares whether the author uses braces for blocks - when you load
the file, it will use indentation the same as you've always used. For
that matter, who cares whether the author wrote "a b +" or "(+ a b)"
or "(add a b)" or "please add a and b" or whatever - as long as you
see it as "a + b" that's fine.

-- 
Steve Horne
steve at lurking.demon.co.uk