Closed Bug 7285 Opened 26 years ago Closed 26 years ago

variable shadowing problems in xpconnect

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: bruce, Assigned: jband_mozilla)

Details

/home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp: In method `nsresult nsXPCWrappedJSClass::CallMethod(class nsXPCWrappedJS *, uint16, const class nsXPTMethodInfo *, struct nsXPTCMiniVariant *)':/home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp:337: warning: declaration of `param' shadows previous local/home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp:338: warning: declaration of `type' shadows previous local/home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp:483: warning: declaration of `param' shadows previous local/home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp:484: warning: declaration of `type' shadows previous /home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappednativeclass.cpp: In method `JSBool nsXPCWrappedNativeClass::CallWrappedMethod(struct JSContext *, class nsXPCWrappedNative *, const class XPCNativeMemberDescriptor *, JSBool, uintN, jsval *, jsval *)': /home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappednativeclass.cpp:513: warning: declaration of `param' shadows previous local/home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappednativeclass.cpp:514: warning: declaration of `type' shadows previous local /home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappednativeclass.cpp:572: warning: declaration of `param' shadows previous local /home/bruce/sandbox/mozilla/js/src/xpconnect/src/xpcwrappednativeclass.cpp:573: warning: declaration of `type' shadows previous local
Assignee: dp → mccabe
Assignee: mccabe → jband
Passing this on to John.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Thanks. But the code is fine. The shadowing is valid. I'm not inclined to change the param names to avoid this over-agressive warning.
Status: RESOLVED → VERIFIED
Verified Invalid
You need to log in before you can comment on or make changes to this bug.