Re: 2 character comment starter bug

[Stefan]

>> But does it matter in such a case whether it has punctuation syntax or
>> symbol syntax?  Do you also give symbol syntax to the / 
>> directory separator as well?

> A / is an illegal character in any part of a filename on this system.
> In this language / / are most often seen as paired delimiters.

Then, what about !, @, #, $, %, ^, &, *, _, +, ,, <, > ., ?, :, ;, |, ... ?

> [#set foo [bar]] and [#set foo [#compute bar + 1]] would be required
> to accomplish the operations your examples seem to describe.
> If I see ':=' in this language I would almost certainly want it
> treated as a word.

Let me ask the question more directly, then: is "foo=bar" one token
or three?

> In this language == always begins a comment no matter where it is
> found unless a ~ precedes it.  There are no exceptions.

Yes, you made that clear in your original message.

>> The current behavior is buggy (it doesn't behave consistently between
>> things like forward-sexp, backward-sexp, and parse-partial-sexp).
>> 
>> But before someone can convince me to try and fix these bugs,  they
>> should first make a good case that the way they setup their
>> syntax-tables is well thought out.

> If the fact that the problem exists reflects the standard by
> which `well thought out' is measured you're being a pushover.

I don't understand this paragraph, sorry.  But just to make it clear: if you
read my above text, you'll note that I do not claim these are not bugs
and/or shouldn't be fixed.

> If it will remain this way for any length of time though, I do
> think it should be documented somewhere.  Even if only on a known
> problems list.

Patches welcome,


        Stefan