[antlr-interest] C# target: .NET Frameworkbug causing NullReferenceException, must use this workaround

[Sam Harwell]

I’m with Jim on this – if I had only sent you a link to the bug report at MS you would have figured out something similar to what I wrote anyway. When you make the change, make sure to comment that you’re working around anti-documented behavior so no one wants to change it later.

 

The standard says this at the end of page 201 (section 14.7.4 Addition operator):

“If an operand of string concatenation is null, an empty string is substituted.”

 

Sam

 

From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-bounces at antlr.org] On Behalf Of Jim Idle
Sent: Saturday, August 09, 2008 11:22 AM
To: antlr-interest
Subject: Re: [antlr-interest] C# target: .NET Frameworkbug causing NullReferenceException, must use this workaround

 

On Sat, 2008-08-09 at 15:05 +0200, Johannes Luber wrote:And did you sign the ANTLR Contribution 

 
License? Otherwise I can't use your bugfix.


I don't think that is true - it is a few lines that you are going to type in yourself, probably fairly differently. Hence this is covered by your own signature I should think. I rarely (ok, never) type in a bug fix that someone sends in, I just use it as an example of HOW something MIGHT be fixed IF the behavior it purports to fix IS in fact the behavior that is wrong ;-)

Jim 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.antlr.org/pipermail/antlr-interest/attachments/20080809/e7cb9974/attachment.html