xpidl should warn on out-of-range constant

RESOLVED WONTFIX

Status

()

Core
XPCOM
P3
enhancement
RESOLVED WONTFIX
18 years ago
10 years ago

People

(Reporter: Michael Ang, Assigned: David Bradley)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
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.

Comment 1

17 years ago
I think this is a libIDL issue.  Andrew?
Assignee: mccabe → andrewtv
WONTFIX?
Assignee: andrewtv → dbradley
QA Contact: mike+mozilla → pschwartau
WONTFIX, unless we rewrite atop a different IDL parser (which is sometimes
tempting, I confess!).
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WONTFIX

Updated

10 years ago
Component: xpidl → XPCOM
QA Contact: pschwartau → xpcom
You need to log in before you can comment on or make changes to this bug.