"EnTerr" wrote:
"TheEndless" wrote:
As I mentioned earlier in this thread, there's at least one roXXXXEvent type that implements ifInt.
If by any chance you ever recollect (or re-encounter) which one, pls let me know - i am most interested to explore it
Looks like it's the roUniversalControlEvent.
"EnTerr" wrote:
I have some serialization methods that don't trust "duck typing" for obvious reasons. I also have some casting/conversion functions that need to know the real type.
Huh. That's actually very un-obvious to me. Can you give me some examples, practical things that caused your mistrust?
You're misinterpreting my use of "trust". It's not that I don't trust that something with the roInt interface will behave as an integer. It's that, if I'm serializing the data for error reporting, for example, I want to serialize the entire object, not just the roInt or roString values.
"Komag" wrote:
I don't recognize the "next"s - they replace END FOR? Are they more useful in some way, such as helping with some version of EXIT FOR or other option?
NEXT is identical to END FOR. NEXT is what VBScript/Visual Basic/Basic uses, so it's available as a convenience.
