 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Sun Dec 09, 2007 1:00 am
[2.16] @{COMVar.Method(params)} fails to pass params (not Major)
|
Again not major, and probably something to think about for the next public version.
Pretty simple one to test. You can do it any session.
| Code: |
| a=%session;#CALL @{a.EchoStr("abc",7)} |
It just gets annoying when combined with the character before @ breaking the DOT. I am going to assume this also affects #FUNCTIONs since it didn't work with them before. Interestingly the compiled code for the #CALL is
| Code: |
0000 PUSHEXP 0016
0008 JUMP 0048
0016 VARREF a.EchoStr(abc,7) <?> (class untitled)
0048 CMD call (1) |
Which is vastly different then the compiled code for #CALL @a.EchoStr("abc",7)
| Code: |
0000 PUSHEXP 0016
0008 JUMP 0080
0016 VARREF @a <?> (class untitled)
0036 LITERAL "abc"
0048 INT 7
0056 STR 'EchoStr'
0072 DOT (2)
0080 CMD call (1) |
I think it would be nice at some point down the road to get the use of braces to work with parameter portions. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Mon Dec 10, 2007 3:43 am
|
Confirmed.
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Dec 11, 2007 6:37 pm
|
Added to bug list
|
|
|
|
|
|
|
|
