a bunch of new stringtemplate and antlr releases

[Terence Parr]

Hi,

release candidate 2 for ANTLR 3.5, ANTLRWorks 1.5, and ST 4.0.7 are now available:

http://www.antlr.org/download/
http://www.antlr4.org/download/
http://www.stringtemplate.org/download/

Please check them out. If there are no problems, we will go final this week. 4.0 in next email.

Ter

[Benjamin S Wolf]

There seems to be a (minor?) issue with 3.5rc2; I'm getting a flood of warning(24)s for:

no such property or can't access: null.attributes

no such property or can't access: null.nodes

3.5rc1 isn't giving these warnings. (Both still produce a correct parser.)

Not sure what changed between rc1 and rc2 that caused these, but there appears to be a commit by sharwell that claims to fix them for Java. I can look into a fix later this week for Python and Python3, but I'd guess this might be occurring for all targets other than Java included with 3.5.

--

[Sam Harwell]

These warnings were unintentionally suppressed previously, and indicate a template making incorrect assumptions about the input. I expect other targets to result in a varying number of these messages until those authors have the opportunity to review their templates. Previously the message read “…or can’t access null”, so the tweak to the message should help them track things down as well.

 

--

Sam Harwell

Owner, Lead Developer

http://tunnelvisionlabs.com

--
You received this message because you are subscribed to the Google Groups "stringtemplate-discussion" group.
To post to this group, send email to stringtempla...@googlegroups.com.
To unsubscribe from this group, send email to stringtemplate-dis...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Terence Parr]

Yeah, previously we simply did nothing when somebody tried to access a null property name. It's really an error though. You can make a listener that ignores those if you want.
T

[Benjamin S Wolf]

It turned out to be easy enough to fix, using the Java commits as reference.

--

[Mike Lischke]

Sam, is it possible to suppress those warnings with a command line switch? I can't do anything about the null accesses, but the warnings will cause my builds to fail.

Thanks,

Mike

[Sam Harwell]

Hi Mike,

 

For now there isn’t. Hopefully it will be resolved for the next release.

 

Which target is this again?

 

--

Sam Harwell

Owner, Lead Developer

http://tunnelvisionlabs.com

 

From: stringtempla...@googlegroups.com [mailto:stringtempla...@googlegroups.com] On Behalf Of Mike Lischke
Sent: Thursday, February 28, 2013 8:43 AM
To: antlr-di...@googlegroups.com
Cc: stringtempla...@googlegroups.com
Subject: Re: [antlr-discussion] a bunch of new stringtemplate and antlr releases

 

Sam, is it possible to suppress those warnings with a command line switch? I can't do anything about the null accesses, but the warnings will cause my builds to fail.

--

You received this message because you are subscribed to the Google Groups "stringtemplate-discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to stringtemplate-dis...@googlegroups.com.

To post to this group, send email to stringtempla...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/stringtemplate-discussion/-/7o0NB4n577QJ.

[Patxi Sanchez]

Hi Mike,

I have exactly the same problem. I can not remove these warnings and my build (MSBuild) fails in each compilation. Did you resolve in any way?

Thanks in advance!

Patxi.

[Mike Lischke]

I have exactly the same problem. I can not remove these warnings and my build (MSBuild) fails in each compilation. Did you resolve in any way?

No, I never used 3.5 because of that. Now I'm moving to ANTLR4, so it doesn't affect me anyway.

Thanks in advance!

Patxi.

El jueves, 28 de febrero de 2013, 15:42:59 (UTC+1), Mike Lischke escribió:

Sam, is it possible to suppress those warnings with a command line switch? I can't do anything about the null accesses, but the warnings will cause my builds to fail.

Thanks,

Mike

On Tuesday, December 18, 2012 3:02:14 PM UTC+1, Sam Harwell wrote:

These warnings were unintentionally suppressed previously, and indicate a template making incorrect assumptions about the input. I expect other targets to result in a varying number of these messages until those authors have the opportunity to review their templates. Previously the message read “…or can’t access null”, so the tweak to the message should help them track things down as well.

Mike

-- 
www.soft-gems.net

[Patxi Sanchez]

Thank you very much Mike, for your quick response.

Finally I managed to solve the problem using ANTLR version 3.4 compiler. Previously, it has been necessary to fix a small typo error in the C.stg template. But now, it is already working properly.