secondlife / jira-archive

2 stars 0 forks source link

[BUG-6657] Valid JSON numbers like 0e0 no longer valid after 14.06.26.291532 #14491

Open sl-service-account opened 10 years ago

sl-service-account commented 10 years ago

Steps to Reproduce

Run this script in a LeTigre 14.06.26.291532 or BlueSteel 14.06.26.291532:


default
{
    state_entry()
    {
        integer type = llGetListEntryType(llJson2List("0e0"), 0);
        if (type == TYPE_STRING) llOwnerSay("TYPE_STRING");
        if (type == TYPE_FLOAT) llOwnerSay("TYPE_FLOAT");
    }
}

Actual Behavior

TYPE_STRING

Expected Behavior

TYPE_FLOAT

Other information

In Second Life Server and Magnum it works fine. Apparently the fix for BUG-6466 (MAINT-4187) broke it. EDIT: In general, it affects a mantissa of zero followed by an e.

Links

Related

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-6657 | | Summary | Valid JSON numbers like 0e0 no longer valid after 14.06.26.291532 | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Sei Lisa (sei.lisa) | | Created at | 2014-07-11T22:05:14Z | | Updated at | 2014-07-14T15:09:00Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2014-07-14T10:08:57.855-0500', "Is there anything you'd like to add?": 'In Second Life Server and Magnum it works fine. Apparently the fix for BUG-6466 (MAINT-4187) broke it.', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'TYPE_STRING', 'What were you doing when it happened?': 'Run this script in a LeTigre 14.06.26.291532 or BlueSteel 14.06.26.291532:\r\n\r\n{code}\r\ndefault\r\n{\r\n state_entry()\r\n {\r\n integer type = llGetListEntryType(llJson2List("0e0"), 0);\r\n if (type == TYPE_STRING) llOwnerSay("TYPE_STRING");\r\n if (type == TYPE_FLOAT) llOwnerSay("TYPE_FLOAT");\r\n }\r\n}\r\n{code}\r\n', 'What were you expecting to happen instead?': 'TYPE_FLOAT', 'Where': 'RC Letigre, RC BlueSteel sims', } ```
sl-service-account commented 10 years ago

Maestro Linden commented at 2014-07-14T15:08:58Z

Hi Sei, thanks for the report. Like you said, it appears that this bug affects numerals with a mantissa of '0' (without any decimal; '0.0e*' should be unaffected).