Am 30.06.2005 um 21:24 schrieb Norman Palardy:
Moreover, the fact, that you can't use parens at certain position
due to this bad language design issue, is absolute contra-intuitive.
I agree that parens should be usable just about anywhere we want
just to force evaluation order and I still dont understand why the
example you posted with
"the beginning" + (New Date()).SQLDate() + "and the end"
did not work as it use parens to try and force the order but
results in a syntax error ....
As Mars wrote
It has nothing to do with conversions. All it takes is this:
foo(bar).baz
Does that mean "call foo, passing in bar, and call baz on the
result", or does it mean "evaluate bar, call baz on its result, and
call foo on its result?"
Thus, the fact that you can call sub's without parameters makes
the above ambiguous. To resolve this ambiguity, the implementor
of the parser defined special rules....
But I wonder, why this isn't defined by means of precedence rules.
If either () or . would have higher precedence, the expression would
be unique.
Kinds
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|