https://issues.dlang.org/show_bug.cgi?id=13307

briancschott@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |10233

--

https://issues.dlang.org/show_bug.cgi?id=13307

Orvid King <blah38621@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |blah38621@gmail.com

--- Comment #1 from Orvid King <blah38621@gmail.com> ---
I believe this was intended to be an alias for near ptr, not short ptr. Although there may be another pointer size possible that I'm not currently thinking of.

--

https://issues.dlang.org/show_bug.cgi?id=13307

--- Comment #2 from Orvid King <blah38621@gmail.com> ---
A small snippet from the ASM parsing in Mono-D:

case "near":
case "far":
case "byte":
case "short":
case "int":
case "word":
case "dword":
case "qword":
case "float":
case "double":
case "real":
    // TODO: Put this information in the AST
    Step();
    if (laKind == Identifier && la.Value == "ptr")
            Step();
    else if (t.Value != "short")
        SynErr(Identifier, "Expected ptr!");
    else if (!(Parent is AsmStatement.InstructionStatement) ||
!((AsmStatement.InstructionStatement)Parent).IsJmpFamily)
        SynErr(Identifier, "A short reference is only valid for the jmp family
of instructions!");
    return ParseAsmExpression(Scope, Parent);

--

https://issues.dlang.org/show_bug.cgi?id=13307

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P3

--

https://issues.dlang.org/show_bug.cgi?id=13307

--- Comment #3 from dlangBugzillaToGithub <robert.schadek@posteo.de> ---
THIS ISSUE HAS BEEN MOVED TO GITHUB

https://github.com/dlang/dlang.org/issues/4034

DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB

--