Documentation

[Charles Pegge]

but you will be overflowing into unallocated space. Allocate some more chars:

Code: [Select]

CHAR c[100] = "Test string"
c += " - more text"
print c


[José Roca]

It was too good to be true

[Aurel]

It was too good to be true

Yes Jose o2 in many things is excellent 

[JRS]

It was too good to be true.

Why no one uses SB. 

[JRS]

José,

The O2 docs in development on your WinPBX repository are looking good.

If Charles doesn't want to expand on his repository, I think a project repository needs to be setup for source control and documentation.

I think there should be two branches. What we have now and Charles's new self compile direction.

[Charles Pegge]

The core is mostly the same, but there are a few changes like Booleans producing 1 instead of -1.

[José Roca]

I have completed another documentation page

https://github.com/JoseRoca/WinPBX/blob/master/docs/Oxygen/Control%20Flow.md

[JRS]

Outstanding!

Thanks for your efforts. Obtaining your interests is like hitting the jackpot.

[Mike Lobanovsky]

Thank you, José!

[JRS]

Maybe it's just me but developing O2 docs on a PowerBASIC repository makes this project seem like PBLite. 

I would be happy to create an O2 project repository and make Charles and José administrators.

If we had a source control repository maybe Charles could acquire some help rather than only accepting example results of his efforts.

[José Roca]

They're simply draft pages.  They can be copied, revised and updated later in an O2 repository. Meanwhile, I have to keep them somewhere.

[JRS]

Agreed.

My point is we need to get source control going. Zips on a Github repository isn't its purpose.

I think Gitlab has a server version that would allow O2 a private repository with markup docs if that would solve the private ownership concerns.

[Charles Pegge]

Many thanks, José. That is very clear documentation, and the style is attractive.

But one point I need to make is that o2 has case-sensitive modes to cope with C-headers, like gl.h. If we use #case capital, then fully capitalised keywords will not be recognised.

[José Roca]

Then I will have to change everything to lowercase. I'm not certainly the best suited to write O2 documentation, because I still don't fully know the language (I'm learning it while I try to write the documentation), and English is no my mother language, but somebody has to do something about it. If I'm having problems, imagine a beginner...

And what "case capital" does?

[Charles Pegge]

There are 3 #cases:

#case insensitive  'converts words to lowercase 'default

#case sensitive  'no case conversion 'like C etc

#case capital  'convert to lowercase, except for all-uppercase words

C headers often have all-uppercase equates or types with the same spelling as some of their procedure names. And we have to maintain that distinction in order to use such headers unmodified.