Hello Roy!

Wednesday September 25 1996 23:53, Roy McNeill wrote to Andrew Seeger:

AS>> Now i am buggered, what on earth is profiler, i have heard of the

RM> It came with the standalone debugger for BC3, but they dropped it
RM> for BC4 (lazy scum).

They dropped to many good things from BC4 :-)

RM> Similar environment to the debugger, you get to tag lines and/or
RM> functions, then run the program.

[...]

RM> It can point out a line or a function that takes an unusual amount of
RM> time, or a line or function that is called thirty jillion times.

Thanks, i will look into it a little more! As it should be able to help me out
a bit.

RM> Unsuspected timewasting code stands out. For example, it told me
RM> that printing individual characters to the screen is horribly slow,
RM> it's much faster to print them to a string and then print the whole
RM> string in one hit.

Hehehe, i am only new to C programming, but i picked up this in the early
stages of starting.

RM>> Find the library reference manual (*the* most important book once
RM>> you've got the hang of the language) and look up keyboard and i/o
RM>> routines. Write lots of little tiny programs to get the feel of
RM>> them.

Pretty well been doing that, it helps a great deal on the learning side of
things.

RM> Good. Again, keep an eye on the functions that are Borland
RM> specific. There's nothing wrong with using them, of course, but you
RM> can save yourself some trauma if you ever change compilers.

Yes, that i have learnt also, i dont really want to become to Borlandised in
my learning process, because as you say, it may cause some hassles if/when
change compilers, which is quite possible if i outgrow BC3 & BC4.

Thanks for the help.

Regards,
        Andrew.

--- FMail/386 1.02