Wiki improvements
Re: Wiki improvements
@CoderJeff:
A last point for SCREENCONTROL (comparing commit text and fbc source)
In fbc 64-bit:
dim param as longint = &h80000000
initializes 'param' with +2147483648 but not -2147483648
What to choose as initializer value (rather as in the fbc source I guess)?
(but it is probably without consequences)
A last point for SCREENCONTROL (comparing commit text and fbc source)
In fbc 64-bit:
dim param as longint = &h80000000
initializes 'param' with +2147483648 but not -2147483648
What to choose as initializer value (rather as in the fbc source I guess)?
(but it is probably without consequences)
Re: Wiki improvements
The only places the default value of &H80000000 is checked:
- SET_WINDOW_POS ... don't set X or Y position if parameter value is &H80000000
- SET_PEN_POS ... don't set X or Y position if parameter value is &H80000000
- SET_ALPHA_PRIMITIVES ... no change if parameter value is &H80000000
For all other SET_* functions, the parameter value is used as-is.
For all GET_* operations, parameter values (including &H8000000) have no effect.
- SET_WINDOW_POS ... don't set X or Y position if parameter value is &H80000000
- SET_PEN_POS ... don't set X or Y position if parameter value is &H80000000
- SET_ALPHA_PRIMITIVES ... no change if parameter value is &H80000000
For all other SET_* functions, the parameter value is used as-is.
For all GET_* operations, parameter values (including &H8000000) have no effect.
Re: Wiki improvements
@Jeff,
changelog.txt:
changelog.txt:
Does this mean that the new default value of the '-t < stack size >' compiler option has been changed to 8192 KBytes for the freebsd platform? , for 32-bit? , for 64-bit?Version 1.09.0
[changed]
- rtlib: freebsd: minimum thread stacksize 8192 KiB
Re: Wiki improvements
It clearly states: thread stack which is different from application stack, which the -t switch addresses.
Re: Wiki improvements
For the stack size in ThreadCreatefxm wrote:changed to 8192 KBytes for the freebsd platform? , for 32-bit? , for 64-bit?
I just noticed my units are wrong - should be 8192 BYTES minimum for FreeBSD. Anything less was causing threading to crash.
On other platforms, the minimum is decided by the pthreads library at the time that fbrt library is compiled.
Re: Wiki improvements
Posts regarding the new '-entry' compiler option have been moved to a new topic in the Documentation forum:
Compiler Option: -entry
Compiler Option: -entry
Re: Wiki improvements
Updated documentation page:
- KeyPgOpProcptr → fxm [added syntax for PROCPTR( identifier, type )]
- to allow getting procedure pointer for based on sub/function type (for fbc version >= 1.09).
Re: Wiki improvements
@Jeff,
I understood through the latest changes (fbc-1.09 08/15/2021) for PowerPC that the documentation needs to be updated as follows:
- On the Compiler Option: -arch page, two new values to add for PowerPC: 'powerpc' and 'powerpc64'.
- New __FB_PPC__ (KeyPgDdfbppc) page to create for PowerPC, as well as all the corresponding links to add to the various pages concerned.
Is it right (I am ready to do it) ?
I understood through the latest changes (fbc-1.09 08/15/2021) for PowerPC that the documentation needs to be updated as follows:
- On the Compiler Option: -arch page, two new values to add for PowerPC: 'powerpc' and 'powerpc64'.
- New __FB_PPC__ (KeyPgDdfbppc) page to create for PowerPC, as well as all the corresponding links to add to the various pages concerned.
Is it right (I am ready to do it) ?
Re: Wiki improvements
You got it right. Thank-you.fxm wrote:Is it right (I am ready to do it) ?
Re: Wiki improvements
Done:fxm wrote: - On the Compiler Option: -arch page, two new values to add for PowerPC: 'powerpc' and 'powerpc64'.
- New __FB_PPC__ (KeyPgDdfbppc) page to create for PowerPC, as well as all the corresponding links to add to the various pages concerned.
- CompilerOptarch → fxm [added two new values for PowerPC]
- KeyPgDdfbppc → fxm [new page '__FB_PPC__']
- CatPgDddefines → fxm [added link to new page '__FB_PPC__']
- CatPgFullIndex → fxm [added link to new page '__FB_PPC__']
- CatPgFunctIndex → fxm [added link to new page '__FB_PPC__']
- PrintToc → fxm [added link to new page '__FB_PPC__']
Re: Wiki improvements
if you get to it before me (changelog.txt probably looks more complicated than it really is):fxm wrote: - CompilerOptarch → fxm [added two new values for PowerPC]
- '-arch powerpc' - big endian
- '-arch powerpc64' - big endian
- '-arch powerpc64le' - little endian
- '__FB_BIGENDIAN__' is defined for 'powerpc|powerpc64' (currently the only two arch's that define it)
Re: Wiki improvements
- CompilerOptarch → fxm [added new value 'powerpc64le']
- CompilerOpttarget → fxm [added new values and shortnames for PowerPC]
Apparently everything else is already up to date.
- CompilerOpttarget → fxm [added new values and shortnames for PowerPC]
Apparently everything else is already up to date.
Re: Wiki improvements
Done:fxm wrote:Proposed warning to add at description paragraph end of SUB and FUNCTION pages:Warning for 64-bit compiler only: Regarding the choice of user procedure identifier names, an additional restriction to the normal Identifier Rules also excludes in the global namespace all register names or other symbols from the assembler format used, because causing assembler errors or runtime bugs (due to the 64-bit compiler not decorating procedure names).
- KeyPgSub → fxm [added warning on choosing user procedure identifier names for 64-bit compiler only]
- KeyPgFunction → fxm [added warning on choosing user procedure identifier names for 64-bit compiler only]
Re: Wiki improvements
As not everyone knows the assembler I wonder if a list of the forbidden words should not be added.
Re: Wiki improvements
An exhaustive list of forbidden register and symbol names (for 'intel', 'att' assemblers) must be precise and exact, so everything should be tested !