From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE: Sugestion: prototype completion
Date: Wed, 28 Apr 1999 18:23:38 -0300
Organization: BrunNet
Lines: 27
Message-ID: <37277C5A.5371B6FE@unb.ca>
References: <3 DOT 0 DOT 5 DOT 32 DOT 19990403081528 DOT 007e0690 AT 200 DOT 252 DOT 238 DOT 1> <3 DOT 0 DOT 5 DOT 32 DOT 19990428011527 DOT 009dcc10 AT 200 DOT 252 DOT 238 DOT 1> <37275C2B DOT CEC5A114 AT unb DOT ca>
NNTP-Posting-Host: ftnts2c42.brunnet.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.04 [en] (Win95; U)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

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