Hello,
On Thu, 22 Apr 2004 11:48:19 +0100, "Jonathan L Cunningham"
<jlc@sofluc.co.uk> wrote:
>Short list:
> (1) compilation errors in an output window, click on the error and
> it takes you to the correct line of source code.
> (2) Class browser: left-click takes you to the declaration, =
right-click
> takes you to the definition (or something equally convenient)
> (3) syntax colouring
>
>Ok, I could go on, but then it wouldn't be a *short* list. None of the
>above is a huge amount of work ... anyone already done it for C++ ?
In reverse order:
I have done "syntax colouring" for Delphi. In fact it should be called
"lexical colouring" because only a scanner is used to tokenize and a
hashtable to detect reserved words. Easy, provided the editor supports
colours, that is.
Class browser is more difficult because it does need syntax analisys
and library knowledge.=20
=46or error location, you have to execute the compiler collecting the
output. I'm no expert with regular expressions, but I guess it should
be easy to recognize error lines.
--
saludos,
=20
Nico Arag=F3n
NOTE: na-list address only works for messages coming from lists.
Please, write to "nico" at the same domain for direct email.
|