Why are fn params "out of scope"?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Developer - 29 Oct 2003 16:53 GMT

When I run this in the VS.Net debugger:
bool SomeClass::GetData(VariantLikeThing *pValue, size_t
ord, unsigned long ulRowID, bool *pbDeleted)
{
    bool bOK = false;

    unsigned long theOrd = (unsigned long) ord;
    unsigned long theRowID= ulRowID;

The debugger can display the values of theOrd and
theRowID, but says ord and ulRowID are out of scope (even
at the point they are assigned to the local variables).
It is frustrating debugging into functions and not being
able to see the values of the parameters. Yes, I can
usually go up the call stack and (usually) see what is
being passed in, but why should I have to?
Anyone know why this happens?

Reply to this Message

Raj Rangarajan - 29 Oct 2003 23:15 GMT

Is this optimized code? Then yes the deubgger has issues with displaying
variables since it has no idea where they are or the location that the
symbolic informations tells the deubgger is wrong

--------------------

>Content-Class: urn:content-classes:message
>From: "Developer" <anonymous@discussions.microsoft.com>
[quoted text clipped - 33 lines]
>being passed in, but why should I have to?
>Anyone know why this happens?

Reply to this Message

CB - 30 Oct 2003 16:05 GMT

No, this is a debug build, no optimization.

> Is this optimized code? Then yes the deubgger has issues with displaying
> variables since it has no idea where they are or the location that the
> symbolic informations tells the deubgger is wrong

Reply to this Message

Why are fn params "out of scope"?

Free Magazines