CAN-FIND

Fri, 2015-10-30 20:05 — dmarteinson

I'm not quite certain why this particular variation of CAN-FIND doesn't parse, but I get:

org.prorefactor.refactor.RefactorException: can-find.
p:7:8: unexpected token: CAN-FIND

However a lot of other instances of can-find do seem to parse just fine.
Corresponding sample below & as an attachment.

================ can-find.p ================

/*------------------------------------------------------------------------
File : can-find.p
Purpose : demonstrate a parsing error using CAN-FIND
----------------------------------------------------------------------*/

IF NOT CAN-FIND (FIRST Customer
WHERE Customer.Name = "asdf")
THEN
MESSAGE "not reached as there is no such customer".
ELSE
MESSAGE "should not reach this point unless you've added a customer with that name".

Attachment	Size
can-find.p	498 bytes

Proparse discussion

Fri, 2015-11-06 02:59 — john

can-find

Hi David,
I get that error only if I try the parse when "Customer" is an invalid table name. If I first load into proparse the sports2000 project (for example), it parses fine.
Is it possible your proparse environment is simply missing the appropriate table name?
The "unexpected token" error is basically a catch-all, and is rather misleading in this case. It would probably be more sensible if it said something like "unable to understand after...".

Mon, 2015-11-23 22:00 — dmarteinson