[
https://issues.apache.org/jira/browse/GROOVY-8739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul King closed GROOVY-8739.
-----------------------------
Resolution: Duplicate
I believe this was fixed in a recent version:
{noformat}
Groovy Shell (4.0.3, JVM: 1.8.0_282)
Type ':help' or ':h' for help.
-------------------------------------------------------------------------------
groovy:000> /abc/
===> abc
groovy:000>
{noformat}
Note: the parser is now smarter about finding ambiguities but there are still
other places where the ambiguity can occur, e.g.:
{noformat}
groovy:000> println /abc/
groovy:001>
{noformat}
> groovysh can't evaluate slashy strings
> --------------------------------------
>
> Key: GROOVY-8739
> URL: https://issues.apache.org/jira/browse/GROOVY-8739
> Project: Groovy
> Issue Type: Bug
> Components: Groovysh
> Affects Versions: 3.0.0-alpha-3, 2.5.1
> Reporter: Роман Донченко
> Priority: Minor
>
> If you type a slashy string into groovysh, it expects more input instead of
> evaluating it:
> {code:java}
> groovy:000> /abc/
> groovy:001{code}
> I know slashy strings can be ambiguous, but that shouldn't be an issue here,
> since an expression can't begin with a division operator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
