bugDotGNU Portable.NET - Bugs: bug #8208, #endregion tokenisation not...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #8208: #endregion tokenisation not compatible with VS

Submitter:  Russell Stuart <rstuart>
Submitted:  Fri 19 Mar 2004 01:53:16 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  None
Open/Closed:  Closed

Jump to the original submission

Fri 07 May 2004 05:55:55 PM UTC, comment #6: 

patch applied.

Russell Stuart <rstuart>
Group Member
Fri 02 Apr 2004 08:07:54 AM UTC, comment #5: 

This patch makes cscc give errors on the same lines as csc, although the messages are different.

Russell Stuart <rstuart>
Group Member
Wed 24 Mar 2004 02:42:10 AM UTC, comment #4: 

Re VS ignoring everything after the #endregion - so does PNet.  Its just the ; that confuses it.  Hence the bug title - I suspect the tokenisation of the # directives is at fault - it is including the ';' in the #endregion token.  If it regarded the ; as a separate token all would be OK.

Russell Stuart <rstuart>
Group Member
Tue 23 Mar 2004 05:23:09 PM UTC, comment #3: 

#region int  asd ljasljd ljasljd ljasdlj jkahsf lakhsdfl
#endregion int asjhdkahsd ksakd kasd laskjd las

it appears the VS compiler ignores everything after the directive to line end as the snippet above is valid.

Anonymous
Sat 20 Mar 2004 02:14:04 AM UTC, comment #2: 

The comments I added to the other bug apply equally well here.  Sorry for the repetition ...

The code containing construct this does compile under VS.  I have verified this.  I have a copy of VS. Before submitting the bug I put the example given in a file called x.cs, and compiled it.  I did not pass the compiler any special switches.  As the original buig report says, VS did not give any errors or warnings.

I am reporting this because I am in the process of porting NUnit to PNet.  NUnit was obviously developed under VS.  It contains a more complex version of the code submitted.

Its not really about being technically right or wrong.  Its about being compatible with MS's implementation of C#.  I don't know if that is one of PNet's goals, but I thought I would submit it anyway.  If it is not one I PNet's goals I can always submit a patch to NUnit.

Let me know what the decision is.

Russell Stuart <rstuart>
Group Member
Fri 19 Mar 2004 04:30:45 PM UTC, comment #1: 

#endregion; 

Extra semicolon ?

Gopal.V <t3rmin4t0r>
Group administrator
Fri 19 Mar 2004 01:53:16 PM UTC, original submission:  

This code compiles under VS without errors or warnings.  It does not compile under VS.

class X {
  #region
  #endregion;
}

Russell Stuart <rstuart>
Group Member

 

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

Attached Files
file #1167:  endregion.patch added by rstuart (656B - application/octet-stream - diff -Nur)

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

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.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2004-05-07 rstuart Open/ClosedOpen Closed
2004-05-07 rstuart StatusNone Fixed
2004-04-02 rstuart Attached File- Added endregion.patch, #1149

Back to the top

Powered by Savane 3.15-e6e5.
Corresponding source code