Mail Archives: djgpp/1999/04/28/18:00:39
Endlisnis wrote:
> You could then select one
> and press enter, and it would finish the function name, then show the syntax. It
> may be silly to use this for 3-5 character function names, but it would be very
> nice for weird classes with long member names. But it would have to actually scan
> the code for prototype definitions (so it could get the local functions/classes).
> I thought it would be such a valuable addition that I was planning on attempting
> to impliment it and submit it for SetEdit/Rhide, but I realized it was a large
> task and required lots of knowledge of compiler design which I don't have. It
> would need to do all of the proprocessing which could be passed on to "gcc -E",
> but if that was exclusively used it would have to be re-run after each line was
> typed, which might not be too bad on my machine (333MHz) but just wouldn't cut it
> for slow machines. I've added it to the list of things to try to do this summer.
I just thought I would reply to my own letter and say that I'm working on a macro
for SetEdit/Rhide that will do the syntax look-up for you, and it doesn't look that
difficult (so far).
--
(\/) Endlisnis (\/)
s257m AT unb DOT ca
Endlisnis AT BrunNet DOT Net
Endlisnis AT HotMail DOT com
ICQ: 32959047
- Raw text -