[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
2 character comment starter bug
From: |
Bielawski, Richard G. |
Subject: |
2 character comment starter bug |
Date: |
Wed, 23 Mar 2005 08:50:38 -0800 |
I've got comment characters defined like this for tacl-mode
(modify-syntax-entry ?\~ "/" st) ; ~ gets Escape syntax
(modify-syntax-entry ?\{ "<" st) ; comment start {
(modify-syntax-entry ?\} ">" st) ; comment end }
(modify-syntax-entry ?\= "_ b12" st) ; comment start ==
(modify-syntax-entry ?\n "> b" st) ; eol ends == comment
By my understanding == start a comment in all cases except
this: ~== because ~ has escape syntax. But that is not true.
code == This is a comment
code== This should be a comment but isn't!
My testing indicates that if the character immediately prior
to == has word `w' or symbol `_' syntax the == sequence is
not recognized as comment start.
Single character comment starters have no such problem
code{properly recognized comment here}
Richard Bielawski
612-667-5039
- 2 character comment starter bug,
Bielawski, Richard G. <=