groovy

GroovyConsole reports "unexpected token" on method name after @Grab

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 1.8.4
  • Fix Version/s: None
  • Component/s: Compiler, Groovy Console
  • Labels:
  • Environment:
    Windows 7 (64 bit)
  • Testcase included:
    yes
  • Number of attachments :
    0

Description

The following script:

@Grab( group='org.codehaus.groovy.modules.http-builder', module='http-builder', version='0.5.1' )

println "x"

yields "unexpected token: println at line: 3, column: 1"

However, inserting "def z" in a line before println compiles correctly. Oddly, adding parenthesis:

@Grab( group='org.codehaus.groovy.modules.http-builder', module='http-builder', version='0.5.1' )

println ("x")

changes the error to: unexpected token: x at line: 3, column: 10

So, I expect there's something about the syntax of @Grab (or @?) that is allowing for the possibility of more text related to it such that the method 'println' is ambiguous but 'def' clearly terminates the @Grab and starts a new element. A minor thing, but confusing.

Activity

Hide
Permalink
blackdrag blackdrag added a comment -

the problem is more that you cannot yet annotate a method call. We intend to change this in the long term, but we have to diverge from Java on this, since Java annotations don't allow for that at all.

Of course the error message is better in the later case, still it is not accepted by the grammar in both cases.

Show
blackdrag blackdrag added a comment - the problem is more that you cannot yet annotate a method call. We intend to change this in the long term, but we have to diverge from Java on this, since Java annotations don't allow for that at all. Of course the error message is better in the later case, still it is not accepted by the grammar in both cases.

People

  • Assignee:
    blackdrag blackdrag
    Reporter:
    James Higgins-Thomas
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: