Documentation

[JRS]

If a new user of Oxygen Basic were to look at and compile the examples provide in the distribution, there should be no reason one couldn't be productive with the BASIC. Waiting for professional written docs to materialize anytime soon isn't  being realistic.

[Aurel]

https://www.oxygenbasic.org/forum/index.php?topic=1721.msg18550#new

Hi
May i continue with my attempt on o2 help in chm form.
Of course it is not on proffesional level but can be useful ?

[AlyssonR]

Any reference material is always welcome - especially when we have senior moments and forget which dialect we're using. 

[Charles Pegge]

I think good search tools are the key, rather than static documentation. Assuming we will end up with thousands of examples, (currently 1200+), programmers should be able to locate any piece of code that approximates their needs. I find I'm writing far less original code now. It's mostly copy, paste, and adapt.

Oxygen_help.chm is currently more like a dictionary than a full manual. It's contents are sourced from inf\o2keyw.dat, a database of o2 keywords with various links to included examples.

[JRS]

My vote is we expand on Charles's Github repository breaking apart the zips to source controlled pushes and use the Github markup tools for documentation.

I'm winding down my BASIC forum activity and plan to have Script BASIC on BitBucket or Gitlab and part of a major Linux distribution by 2020.

[Aurel]

Any reference material is always welcome -

Ok..
then when i get some free time i will continue in hope that should be useful 

[JRS]

Every contribution to the project by the community matures the BASIC. I think you should dedicate more time toward your English speaking skills which will make your programming topics easier to swallow.

Mike and José are great examples of 2nd language mastering.

[José Roca]

Sorry, but without documentation you're going nowhere.

Examples are useful as a complement to the documentation, not a a substitute. Besides, there are many things whose explanation can't be found in the examples.

For example:

Code: [Select]

#include "$/inc/console.inc"
DIM n AS ULONG
n = -1
print n
waitkey

Why it prints -1 instead of 4294967295.

A bug? A feature?

If you assign -1 to a WORD variable it correctly converts it to 65535.

[Aurel]

Why it prints -1 instead of 4294967295.

 

because is right,

n is defined as INT or UINT
so -1 is a INTEGER.... i don't see problem

[JRS]

Asking questions is another excellent way to refine the understanding of O2.

[JRS]

José,

Curious. Do you have a formal education or are you self taught?

[José Roca]

In programming, self taught. Fortunately, the first PC that I used had a manual.

I learn by practice, but I first read the documentation to know if the lamguage has everything I need. And I hate to ask questions for simple things.

[José Roca]

Another question: The compiler doesn't seem to work with unicode source code files. This means that I can't work with unicode string literals. Am I right?

How do you deference a pointer?

This does not compile:

Code: [Select]

$ FileName  "test.exe"
ASCIIZ s * 260
s = "Test string"
DIM p AS ASCIIZ PTR = @s
print *p

Do you really believe that this is a good way to learn a language?

The natural reaction will be to become angry quickly and send the compiler to hell.

I have collected information about O2 native data types.

See: https://github.com/JoseRoca/WinPBX/blob/master/docs/Oxygen/Data%20Types.md

For operators, I guess that I will have to search in the C++ documentation.