Documentation

[JRS]

You  can use Chrome if you have it to accept the expired cert. I hope to see Let's Encrypt certs soon.

It's true you can't rely on history if you were never there to see it in the first place.

[JRS]

The O2 sandbox has been updated with OXSC181215.

04:27 15/12/2018 Fix Empty macro problem (replacewdt)
22:58 14/12/2018 Appe() uses copy() instead of mid()
18:37 14/12/2018 Fix "=" bug subsas (f=a)
18:35 14/12/2018 Support accum setting with += -= assignments (cpa>2)
04:19 14/12/2018 Revoke class-operators, retain macro-operators(findop)
19:09 13/12/2018 Work on nested scopes for epilog code
00:05 13/12/2018 Merge mcword into replacewdt
14:40 12/12/2018 Remove wword uword parsing (destructors 20)
02:43 12/12/2018 Refactor macso etc. (mac to mrc)
12:00 11/12/2018 Implement bycopy

[JRS]

The O2 sandbox has been updated with OXSC181217.

06:12 17/12/2018 Fix macro insider ## substitution (himac)
14:29 16/12/2018 Fix wide string literal binary encoding (makerecordw)
18:40 15/12/2018 Typeof returning text in chr(34) quotes (pars.inc newline)
06:04 15/12/2018 Revoke 'operator' methods & cleanup (findop)

[Charles Pegge]

My dirty laundry list

I've removed a significant amount of redundant code.

[JRS]

The O2 Sandbox is working again with HTTPS.

Charles,

Rather than waiting to build a OXSC milestone, you can use the sandbox web interface to upload a new version of the file giving it a commit comment.

This way you have better version control and recovery if needed.

A great way to verify your changes in a focused manner. (DIFF)

John

[JRS]

Charles,

When do you think you will start releasing examples tested with the cloning compiler?

[Charles Pegge]

Hi John,

I'm still trying to nail down the set of features required for UDT operators. It has to be efficient down to the bare metal, as well as supporting higher-level types which might involve variants.

[JRS]

VARIANTS. 

I would be happy to do some testing of examples if you can give me a list of OXSC features still in the oven.

[JRS]

Mr. Roca,

Do you still have any interest in continuing on with your O2 documentation project? Can I assume your silence is based on waiting for Charles's OXSC release? I hope I haven't offended you in any way. Not everyone likes what I have to say but that isn't a goal I'm chasing.

[JRS]

The OXSC181230 update is in the sandbox.

I think a good way to learn O2 syntax is reviewing the compiler code itself. Charles has included over 4,500 lines of test code to try as well.

[Brian Alvarez]

If variants are natively supported, i will surely use them instead of my own version. Not that my implementation is bad but the less conversions i have to make, the faster the compilation is.

[Aurel]

Ok
Is there 32 bit version of selfcompiled Oxygen Basic or not?
I mean compiled exe in zip..so that we can try?
thanks

aha ..oK it is in sandBox...
but there is :
rtl32.inc
oxygen.dll


what about gxo2.exe ... or i can use old version ?

[Charles Pegge]

Hi Aurel,

Older versions of gxo2.exe  compile using o2_asmo, which is now obsolete and o2_basic is used instead.

The new oxygen.dll is still a 32-bit replacement for the original.

[Charles Pegge]

Hi Brian,

The latest o2 changes enable Classes/UDTs to be used directly in expressions with operators.

The operator-sets are defined in macros which are called by the compiler when it needs to encode an operation for the type of operand being used in an expression.

To show how it works I can produce a skeleton operator set for variants...

[Aurel]

The new oxygen.dll is still a 32-bit replacement for the original.

HI Charles..

Ok i understand that
Is that mean that i don't need gxo2.exe ?
In that sandBox ..there is no o2_basic.exe ? ...right?
what looks strange to me 

or i must wait for new version which will work with new oxygen.dll ?
I am confused now.... and i don't know what compiler i can call from my editor.

You know that in my programs i use this:
awinh.inc
rtl32.inc
gxo2.exe
AurelEdit.exe or OxIde.exe