If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Update docs to not use intN and uintN types

RESOLVED FIXED

Status

Developer Documentation
Mozilla Platform
P5
normal
RESOLVED FIXED
5 years ago
2 years ago

People

(Reporter: sheppy, Assigned: sheppy)

Tracking

Details

(Assignee)

Description

5 years ago
:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: 13 Branch
 Technical Contact: 

:: Details

The intN and uintN data types were removed in Firefox 13. These are exactly the same as "int" and "unsigned int". Update docs to reflect this change.
If there's any of the following left, maybe they can be changed at the same time:

jsdouble -> double
JSIntn -> int
JSUintn -> unsigned
JSPackedBool -> bool
jsrefcount -> unsigned
jsint -> int32_t (or int)
jsuint -> uint32_t (or unsigned)
int{8,16,32,64} -> int{8,16,32,64}_t
uint{8,16,32,64} -> uint{8,16,32,64}_t
JSInt{8,16,32,64} -> int{8,16,32,64}_t
JSUint{8,16,32,64} -> uint{8,16,32,64}_t

Comment 2

5 years ago
Looking at the bug and patch, it looks like an internal SpiderMonkey change only that should have no impact on JS code.
Looks like Jeff Walden already documented the change at https://developer.mozilla.org/en-US/docs/SpiderMonkey/1.8.8#typedef_Changes

Needinfo'ing Dave Mandelin who filed and fixed bug 730511. If the change was only internal and properly documented by Jeff, feel free to set this documentation as RESOLVED. Otherwise, can you describe how this bug affects JS code? Thanks!
Flags: needinfo?(dmandelin)
It doesn't affect JS. It affects JSAPI documentation, such as:

https://developer.mozilla.org/en-US/docs/SpiderMonkey/JSAPI_Reference/JSNewResolveOp

Comment 4

5 years ago
Ok. Taking the freedom to change the Component then.
Assignee: bruant.d → eshepherd
Component: JavaScript → Mozilla Platform
Flags: needinfo?(dmandelin)
I've removed the few dozen left (I think Arai refactoring removed most of them beforehand).

If you find some left, feel free to fix them, or to file specific bugs; closing this.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.