Closed Bug 205503 Opened 22 years ago Closed 14 years ago

Better type conversion for IDispatch

Categories

(Core :: XPConnect, enhancement)

Product:
Core
Component:
XPConnect
Platform:
x86
Windows XP
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Milestone:
mozilla1.7alpha

People

(Reporter: dbradley, Assigned: dbradley)

References

Details

The IDispatch conversion logic could provide better type conversion support by using VariantChangeType. Currently we rely on the IDispatch system to do type conversion. This limits some conversions, such as the string "True" being converted to a boolean. To date this hasn't caused any problems. I just noticed this in expanding the test case logic. We already have the type information for the parameters, so it shouldn't be hard to implement.
I just want to clarify. This bug may make it seem like no conversion is done. But many are currently perform, such as string to number and visa versa. What isn't done is the string "True" to bool and back, as well as numeric conversion to SCode, and some other lesser used types.
Status: NEW → ASSIGNED
->1.5
Target Milestone: --- → mozilla1.5alpha
Target Milestone: mozilla1.5alpha → mozilla1.5beta
Moving out, speak up if you believe this needs to be considered for 1.5b
Target Milestone: mozilla1.5beta → mozilla1.6alpha
Moving out
Target Milestone: mozilla1.6alpha → mozilla1.7alpha
QA Contact: pschwartau → xpconnect
The IDispatch API was removed in bug 662000. -> INVALID [Filter bugspam on idispatchinvalid]
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.