[Mono-bugs] [Bug 76218][Nor] Changed - Tokenizer/Seekable stream bugs.

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by atsushi at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=76218

--- shadow/76218	2005-09-24 22:18:27.000000000 -0400
+++ shadow/76218.tmp.5041	2005-09-24 22:24:33.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 76218
 Product: Mono: Compilers
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: C#
 AssignedTo: rharinath at novell.com                            
 ReportedBy: miguel at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -44,6 +44,21 @@
 > seen that bug in the past am afraid.
 
 ------- Additional Comments From atsushi at ximian.com  2005-09-24 22:18 -------
 Created an attachment (id=15792)
 not-portable patch to gmcs, comment will follow
 
+
+------- Additional Comments From atsushi at ximian.com  2005-09-24 22:24 -------
+Am attaching this patch due to Miguel's request.
+
+So this patch (against somewhat old mcs though) would solve the
+problem, but it is not portable to gmcs because gmcs depends on  the
+SeekableStreamReader-based repositioning around OP_GENERICS_GT ...
+OP_GENERICS_LT.
+
+To my understanding, it is because otherwise there are unresolvable
+grammar ambiguity in jay. So the possible fix would be 1)return
+differently-defined-but-actually-identical token and 2)manage
+something like tokenization "mode" to switch between generic type
+specifier mode and normal mode (I'm not sure if this really solves the
+problem though).