Mail Archives: djgpp/1999/04/28/17:12:10
Thiago F.G. Albuquerque wrote:
> >> blit_
> >>
> >> and press, say, ^\. And then that "blit" you typed becomes
> >>
> >> void blit(BITMAP *source, BITMAP *dest, int source_x, int source_y,
> >> int dest_x, int dest_y, int width, int height);
> >Are you sure it helps? I don't know, you then must delete the name of the
> >parameters.
>
> Yes... in spite of this, this is an action I do quite often: type the name
> of the function, press ^F1, copy the prototype of the function and paste it
> in the code. I do it to avoid fliping between the editor and the info
> vierwer windows to check the arguments' types (and their order) as I fill
> them.
>
> The original idea was to clone VC++ 6's completion. I didn't see it (yet);
> a friend told me it is really handy. But I think it would be too difficult
> to implement. So, I suggested this instead -- which would already save me a
> lot of key strokes.
I was forced to use VB5 at work. I don't like BASIC, but the interface is
very nice. It uses a similar interface to VC++6. If you type the name of a class
object and a '.' (as well as "->" in C++) and it lists all of the public members
of the class. Also, if you type the name of a function it doesn't actually type
out the prototype, but prints the syntax just below the cursor in a small "Tool
tip" style window. It also offers word-completion with Ctrl+Space (like the
macros in rhide/setedit) where if I typed "po" it would show a small drop down
list with
popen
pow
pow10
pow2
in it (these were the libc entries starting with "po"). 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.
Is there any way to remove the lines like:
# 1 "aa.cc"
# 1 "P:/include/stdio.h" 1 3
from the preprocessor output? (I mean another switch, not the use of program like
sed)
--
(\/) Endlisnis (\/)
s257m AT unb DOT ca
Endlisnis AT BrunNet DOT Net
Endlisnis AT HotMail DOT com
ICQ: 32959047
- Raw text -