Quoting Bert Wesarg <[EMAIL PROTECTED]>:
> As reported here [1], we shuold force a final newline in macro files,
> to prevent syntax errors.
>
> Regards
> Bert
>
> [1]
>
https://sourceforge.net/tracker/index.php?func=detail&aid=2038921&group_id=11005&atid=111005
>
Looks good to me.
Tony
PS re your comments about my fastConcat3 patch: you're right, of course...
I'll need to fix it some time, but I'm very behind in keeping my patch set up
to date. Sorry. The easiest, I suppose, is to return the negative of the
length
and a positive number for failure. A bit unnatural, but there you go...
I've been playing in parse.y, implemented (both)
for ([k] = v in array) { ... }
and
for (v = [k] in array) { ... }
meaning the same thing, and similarly
if (v = [k] in array) { ... }
if ([k] ! in in array) { ... }
ex-or (^^) and conditional (?:) operators; and adding parser location
information so you can go from an instruction to a position in a source code
string. I'd like to get it to the point of being able to provide a debugging
service. But building patch files for each of these and combining with the
others is turning into a real can of worms! We need the next release and a new
branch!
--
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop
