BSTR, WIDE with ASCII conversation.
... SciptO2 1.0.
So how can your SB elaborations help the O2 developer or user's immediate needs?
All compliant BASICs should, as a minimum, be able to run Dartmouth code as-is. All more advanced features of the language are just dialect-specific extensions, regretfully, non-standardized up till now.
A good example of compliant BASIC is your hateful Script BASIC that runs the code snippets from the book I quoted earlier without a single change (except for the DATA/READ commands that wouldn't be hard to fix if need be). There are some other dialects that are able to do the same with equal ease.
And if O2 isn't able to read and execute Dartmouth code (directly or with a dedicated, special-purpose include file) as flawlessly, then I am afraid O2 cannot be called a compliant BASIC, regardless of its versatility and polymorphism.
Script BASIC that runs the code snippets from the book I quoted earlier without a single change (except for the DATA/READ commands)
There are some other dialects that are able to do the same with equal ease
I don't see EZGUI, Brian's BASIC or the external debugger project making any headway either.Although o2debugger is functional I need some feedback to make it evolve or at least fix bugs.