Closed
Bug 55203
Opened 24 years ago
Closed 20 years ago
xpidl should warn on out-of-range constant
Categories
(Core :: XPCOM, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mang, Assigned: dbradley)
Details
If you specify a constant that is too large for its storage type, then you will get a pseudo-random value in your header file and typelib. e.g. const long qux = 233232132132131321123213; const long quux = -121212121212212121212121; Get you -1 and 0 respectively. I'm not actually suggesting we burn cycles to fix this given that it probably won't come up in practice. Just want to mark this for posterity.
WONTFIX, unless we rewrite atop a different IDL parser (which is sometimes tempting, I confess!).
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•