Re: Two Questions

From: Joe Wright (joewwright_at_comcast.net)
Date: 08/12/04 

Date: Wed, 11 Aug 2004 21:27:09 -0400

RJJ wrote:

> Hi,
>
> Firstly, I've just taken on a large project that looks like it's been
> designed by a 2 year old. It's absolutely jam packed with very large macros
> which invoke other large macros that use do/while, switch/case,
> token-pasting, gotos etc. which I'm finding very difficult to debug. Is
> there a piece of software/utility that will unravel/unroll/convert these
> ridiculous structures into inline functions, or is there a way to "force"
> the complier to single step through them in debug mode (visual c++ v6.0 on
> XP).
>
> Secondly, I trying to write some information out to a file from a dll I'm
> debugging. Under what circumstances would the program seem to trace through
> the code on a single step debug session but not create the file on the hard
> drive (discount file space, incorrect filename etc - the code works in a
> separate win32 project).
>
> Any help appreciated,
>

Hi yourself. Niether of your questions have to do with the C
programming language. You need to be somewhere people care about
Microsoft Visual Studio. Not here.

Having that off my chest, macros can be hard to read. My C compiler
allows me to write an intermediate file of the preprocessed source
in which the macros have disappeared and their results remain. 

-- 
Joe Wright                            mailto:joewwright@comcast.net
"Everything should be made as simple as possible, but not simpler."
                     --- Albert Einstein ---

Relevant Pages