Posted: Fri Jun 18, 2004 5:21 pm
mmm why would it be confusing? it's rather simple: use the last type def the compiler encountered
if one adds the type def to the pointer, from that moment on the def changes
i agree that if a change would be temporary the use of parenthesis would be better
*a.(lasjdf)\asdf = asdfasdf
but it will raise quite a few questions with the crowd... i'd suggest to move the last parenthesis:
*a.(asdf\asdf) = asdfasd
or perhaps use a different type of bracket, dunno
*a.[asdf\asdf] = asdfasd
square brackets have a slight preference for me, as in (most) basics normal parenthesis are 'enclosures' of functions or expressions, but not an inherent part of the syntax, they might cause some confusion with dimmed stuff...
dim *a.b(100)
*a(x) = 5
*a.(x)\b = 5
while square brackets in a different place are slightly easier to read:
*a.[x\b] = 5
if one adds the type def to the pointer, from that moment on the def changes
i agree that if a change would be temporary the use of parenthesis would be better
*a.(lasjdf)\asdf = asdfasdf
but it will raise quite a few questions with the crowd... i'd suggest to move the last parenthesis:
*a.(asdf\asdf) = asdfasd
or perhaps use a different type of bracket, dunno
*a.[asdf\asdf] = asdfasd
square brackets have a slight preference for me, as in (most) basics normal parenthesis are 'enclosures' of functions or expressions, but not an inherent part of the syntax, they might cause some confusion with dimmed stuff...
dim *a.b(100)
*a(x) = 5
*a.(x)\b = 5
while square brackets in a different place are slightly easier to read:
*a.[x\b] = 5