[Mono-bugs] [Bug 378465] New: Parser inconsistency with the specification suspected.

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Apr 9 13:44:46 EDT 2008


https://bugzilla.novell.com/show_bug.cgi?id=378465


           Summary: Parser inconsistency with the specification suspected.
           Product: Mono: Compilers
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: C#
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: david.cole7 at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Description of Problem:

Not really a problem, but I have noticed a slight inaccuracy in the jay file,
between what it does and what is detailed in the EMCA Specification.  

The problem concerns the rule namespace-name, which in the specification is
defined as a namespace-or-type-name, but reading through the spec, this is
slightly misleading.

Steps to reproduce the problem:

If you had a cs file along the following lines:

namespace a::b
{
//CODE
}

Actual Results:

Monodevelop, which uses a Coco/R based parser, will have a parser error of a
'{' expected, which makes sense.

gmcs currently compiles this, and checking the generated assembly the namespace
is generated correctly, but should it not been flagged as an error? 

Expected Results:

The Microsoft compiler will flag a syntax error, that it expected a '.', as in
the description in the spec it states that a namespace-name will not have type
parameters, and will also not be a qualified alias

How often does this happen? 

Every time as it is in the Parser

Additional Information:

I could problem create a patch for this if it is a true bug, or if this grammar
rule has been left as this for a reason, I don't think this is too serious of a
problem.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the mono-bugs mailing list