Strongly scoped transaction on the same buffer twice gives m

When you erroneously define the same buffer twice in a do for loop you get a very misleading error message. Took me ages to track this one down. OE11.6 and it's in 10.2B07 as well. Would you say this is a bug? Shouldn't the compiler error on the duplicate buffer scoping?

---------------------------
Error (Press HELP to view stack trace)
---------------------------
** Name is ambiguous with bcustomer.Name and bcustomer.Name (72)
** C:\Users\James Palmer\Progress\Developer Studio 4.3.1\workspace\DBA Challenge\CreateTraffic.p Could not understand line 26. (196)

---------------------------
OK Help
---------------------------

Code, obviously very simplified:

define buffer bcustomer for customer. 
do for bcustomer, bcustomer transaction:
    for each bcustomer no-lock
        where bcustomer.Name eq 'JP':
    end. 
end.