Hi Mars,
RBScript and its context has apparently been made more strict (even more
restrictive).
I don't recall making any such change intentionally; what is it that
leads you to this conclusion?
That's what I thought. I found nothing in the release notes that would
explain it.
This I found no longer working:
Script:
Sub SomeSub( s As String )
C_SomeSub( s )
End Sub
Context:
Sub C_SomeSub( v As Variant )
This won't work in 2006 anymore. Minor issue, since you can do:
Sub C_SomeSub( s as String )
Dim v As Variant=s
Still, I had planned to use variants more, not less. Some functions that I
had planned cannot be implemented.
The other issue that cost me a bit more aggravation (in the end, I could
work around it, so for me this is no immediate show stopper either): It
appears you can no longer pass an object through the context in either way.
I know, it was never officially supported, so I shouldn't whine about it.
Still...
Same here, I had planned to exploit this some more.
One other issue I'm still investigating that I cannot explain yet. In one
particular case I find that overloading a certain function causes the
compiler to bark at me "There are several items with this name and it is not
clear which one the call refers to". That function used to work, but no
longer in RB2006.
Frankly, I was disappointed to find how little improvement was made to
RBScript. It is such an awesome part of RB that deserves more attention from
RS than it currently (apparently) has.
Ronald Vogelaar
--
http://www.rovosoft.com
_______________________________________________
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>
