Today's mainframeanything to new 557
(Charles Shannon Hendrix) writes:
Either that or (in the case of my Win98 box), the memory locations the program scribbles on moves from a critical area to an unused one.
Of course there is measurement and security overhead; but you are in error about performance and security monitoring being contrary. They are different views of the same observations. The...
Granted. Some of them take a lot of getting used to, though. In my case (Borland C++ Builder 4), you have to go through creating a "project", reproducing the functionality of a makefile, and all sorts of bureaucratic things that create disk overhead several times the size of all files used in my makefile environment. The time this takes far exceeds the time needed to create a test version of the program with a few log file writes added. Plus I get the feeling that switching to an IDE required an emotional commitment to that IDE - but I was always suspicious of vendors' love of putting you on a path from which there is no return.
That's understandable if the debugger isn't compatible with that environment.
Agreed. I love the one that came with my old MS-DOS Lattice C compiler - normally I can compile with makefiles, but I also have a batch file that will compile one program with debugging options set. The result can be run by the free-standing debugger that came with the compiler - which gives me the best of both worlds.
Someday I hope to find the time to search for something as nice that runs under Windows or Linux - but so far I've been happy enough with things as they are to not bother.
-- I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
Today's mainframeanything to new 558
Alt Folklore Computers from Newsgroups