[ https://issues.apache.org/jira/browse/FELIX-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747159#action_12747159 ]
Derek Baum commented on FELIX-1325: ----------------------------------- FELIX-1325-2.patch looks good - let's apply it and move on. It's actually a superset of FELIX-1520.patch, and that's OK too. > gogo doesn't report a command not found error unless an argument is supplied > ---------------------------------------------------------------------------- > > Key: FELIX-1325 > URL: https://issues.apache.org/jira/browse/FELIX-1325 > Project: Felix > Issue Type: Improvement > Components: Gogo > Reporter: Derek Baum > Assignee: Guillaume Nodet > Priority: Minor > Attachments: FELIX-1325-2.patch, FELIX-1325.patch, FELIX-1325.patch, > FELIX-1325.patch > > > 2009/7/13 Hiram Chirino <chir...@gmail.com> wrote: > But on related note... to the gogo developers: I would have expected a > command not found error when you type in a command that's not found. This > seems to work fine if you pass an argument to a command. It this a > 'feature' or a bug? > This is a 'feature', in that an undefined command silently returns itself, > rather than an error. > This is so that: > > x = hello > works; otherwise the assignment would fail, with a command not found error. > Note: that > > x = hello world > will actually evaluate the 'hello' command with 'world' as an argument. > > x = "hello world" > tries to evaulate the 'hello world' command, which probably doesn't exist, so > it falls back to returning the value, rather than unknown command. > I think this can be simply resolved by avoiding re-evaluating an assignment > with a single argument. > This will mean that > > x = hello > works as it does currently, but that > > hello > will fail with 'unknown command', rather than simply return itself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.