bugUnofficial CHM Specification - Bugs: bug #30093, Variable type (Signedness) of...


bug #30093: Variable type (Signedness) of specification fields

Submitter:  Marco van de Voort <marcovje>
Submitted:  Wed 09 Jun 2010 09:38:56 AM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Wed 09 Jun 2010 09:38:56 AM UTC, original submission:  

Many values in the spec are "dword" while signed values are assigned to them (usually -1 as special value).

This causes problems in FPC when people compile with extra runtime checks (that check ranges strictly). We can adjust the typing to signed (but that is a specification discrepancy), hence we decided to ask this upstream.

We can also disable checks for those units. (in theory we can also typecast each and every assignment but that is too painfull), but that is not so elegant.

Possible solutions: adapt types, or define the <0 cases not as -1 but as dword(-1) or $FFFFFFFF

Free Pascal mantis bug reference : 16669

Marco van de Voort <marcovje>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by marcovje (Submitted the item)
  • -email is unavailable- added by marcovje

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-06-09 marcovje Carbon-Copy- Added marcovje

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code