Tutorials are in the official FreeBASIC documentation too, however,
they may not be up to date: FB-Documentation (see Community Tutorials)
Some thoughts and ideas concerning: beginners & Libraries

I also think you arbitrarily assign the cause, ... Could you please, be a bit more specific, on that "arbitrarily" statement? I think that I've explained later on sufficiently, what is meant in the first statement. To be honest, not really looking for opinions, just to let users know it's...

deltarho[1859] wrote:The phrase is actually 'Apples vs oranges'.

While this may be correct in english, in german, we like to be, from afar different: it's as written ;-)
(since both of them, are still fruits, right?)

I don't quite understand why the return is Long, but: Dim As ULong mode, cnt = 1 Dim As UShort w, h, cd = 32 ' cd = color depth (in bit's) ' macros: v (value) is converted to ULong (32 bit) then filtered (to 16 bit) ' since 'built in' macros cast to UInteger, they're considered "unsafe" in...

Just for fun (with code by: zxretrosoft): Loop Until, sped up by using AndAlso (instead of, And) loop until (h1=ps1 AndAlso h2=ps2) AndAlso (h3=ps3 AndAlso h=x) + used fbc64 ver. 1.05.0: -s console -gen gcc -O 3 -fpu sse runtime = approx.: 4.11 Seconds !!! <-- if you want to do: speed comparisons, p...

Perhaps, but currently, ULong pallette arrays do not work with FBC-64. This is due to: legacy language mode = QB! The Ball & Chain, on FB's legs ... Even if QB afaik, had type Long = 32 bit int type (Integer, in QB = Short in FB). This is the reason, that GFXLib2 requires "Integer" as...

... the declared type of palette array should always be an U/Integer (32-bit or 64-bit, depending on the platform) This is clearly (from a memory allocation point of view), the wrong approach, since any 32 bit's color should only ever be represented by ULong! (fixed unsigned 32 bit type, uint in &q...

@coderJeff, H & W are DWORD on windows and __u32 on linux (i.e. ULONG SHORT ) at the API Aka: H = WORD, L = WORD (USHORT) ... by M$'s definition of data-types, as well as __u32 seems to be ... (I'm not 'a jour' on LIN-vars.). the Field=1 statement in -lang FB has only an effect if: 1) the defaul...

Btw: it is the very same, with: "Protected:" access ...

sancho3 wrote:SUB somesub2(/'this parameter defaults To byref '/ zzz as type__t)

Sorry, this is incorrect, because "not stated passing method" defaults to: ByVal, except in
cases, where default ByRef is implicit (Array's passing, where "specifiers" are forbidden).

Well, that truely clears yet another one, of those mysteries ... thanks.

A Note on doc, related to Private: should imho state:
Everything with "private" access, cannot be inherited, as opposed to "protected" access rights.

Should have known that, because I've checked the manual on those, yesterday. However, apart from mentioning "inheritance" on Protected, there isn't much on: details on them, or a direct comparison (except as stated above). What you are saying is: Private: Type.Member isn't "inheritabl...

What is the "overloaded" expression, a parameter declaration? Just a 'proxy' or 'dummy' for any variables etc. What I gathered from your article: 1) if a overloaded Constructor exists, then implicit, default Constructor is destroyed! 2) since a derived type always calls: Base() Constructo...

Because for me, the answer is obvious and more general: A procedure (declared for any reason) may have no implementation (no body defining) if it is never actually called in the program. This isn't what I mean by Implementation: "do I have to write out such 'empty body' thingy? That's the real...

dim as integer opt_width = 1920 dim as integer opt_height = 1080 dim as integer opt_depth = 32 had to be done (FBC 64, 1.05/1.06), as dodicat describes ... multiple Sleep statements (before each End x, statement) recoded SCREEN_MODE_SIZE: ' since field alignments are useless (doesn't change anythin...