Wiki improvements
Re: Wiki improvements
I read also this but it's more like an example for finding an explicit name.
Re: Wiki improvements
changelog.txt:
Documentation update:
- CompilerCmdLine → fxm [default stack size doubled for 64-bit targets]
- CatPgCompOpt → fxm [default stack size doubled for 64-bit targets]
- CompilerOptt → fxm [default stack size doubled for 64-bit targets]
- CompilerFAQ → fxm [default stack size doubled for 64-bit targets]
- ProPgDynamicMemory → fxm [default stack size doubled for 64-bit targets]
Version 1.08.0
[changed]
.....
- fbc: double the minimum and default stacksize on 64-bit to 64Kb and 2048Kb respectively.
.....
Documentation update:
- CompilerCmdLine → fxm [default stack size doubled for 64-bit targets]
- CatPgCompOpt → fxm [default stack size doubled for 64-bit targets]
- CompilerOptt → fxm [default stack size doubled for 64-bit targets]
- CompilerFAQ → fxm [default stack size doubled for 64-bit targets]
- ProPgDynamicMemory → fxm [default stack size doubled for 64-bit targets]
Re: Wiki improvements
fxm, you are the best! If it weren't for your help I'm sure I would forget to document ... everything. :)
There's an old post about some missing docs. Exe formats and gfx formats. Do you mind re-posting that? Plus any new stuff? I'll do my best to fill in some details.
There's an old post about some missing docs. Exe formats and gfx formats. Do you mind re-posting that? Plus any new stuff? I'll do my best to fill in some details.
Re: Wiki improvements
I guess you're talking about this one: Missing Documentation
I did everything I could in relation to these shortcomings, but I am reaching my limits of knowledge here.
Missing Documentation
Please edit this page to remove items when they are written or add items when they are noticed.
Missing/Incomplete/Outdated PagesExternal Libraries - availability (windows, linux, DOS), usage, and download locations
Pages missing/incorrect examples
Cross compiling and environment variables (used to invoke sub-programs)
Programmer's Guide (W.I.P.): External Graphics File Formats (page to fill in)
Programmer's Guide (W.I.P.): Executables (page to complete)
Dedicated page for Screen's QB/page-choosing mode - perhaps KeyPgScreenqb? (quick fb example added to KeyPgPcopy for now...)None known (but if found, please edit this page)
Misc wishlistWarn in all non-portable or "evil" examples
Consistent policy about "FB version diff" KeyPgImageInfo KeyPgRem
FB source file size limit
"returning references" stuff (PEEK, (), [], ... total 7 pages BUMP'ed today)
"-gen GCC" document how to get it working (esp. in DOS)
I did everything I could in relation to these shortcomings, but I am reaching my limits of knowledge here.
Re: Wiki improvements
coderJeff wrote: If it weren't for your help I'm sure I would forget to document ... everything. :)
Also my fault because it was my request and we both coded it.
Thank you fxm.
Btw I have to finish some docs about 64bit assembly (requested by D.J.Peter). I hope before end of january.
Re: Wiki improvements
fxm wrote:I guess you're talking about this one: Missing Documentation
Yes, exactly. Thank-you for collecting everything there.
"dedicated page for qb screen statement" was added back in 2009.
@counting_pine, do you remember the reason? I feel like one page for screen should be good.
-
- Site Admin
- Posts: 6241
- Joined: Jul 05, 2005 17:32
- Location: Manchester, Lancs
Re: Wiki improvements
Mainly just to clean things up a bit I think. At the time, I maybe thought that lang qb users could do with more tailored documentation? I don’t know...
I half thought the active/visible page parameters were only available in Lang qb, but it looks like lang fb has its own syntax for that too. Maybe the “Differences from QB” section just needs to be clearer on that.
But since it has the same functionality available as lang qb, splitting the page maybe wouldn’t streamline things that much.
I don’t mind if it stays the way it is, particularly if the issue has been sitting in someone else’s backlog for 11 years!
I half thought the active/visible page parameters were only available in Lang qb, but it looks like lang fb has its own syntax for that too. Maybe the “Differences from QB” section just needs to be clearer on that.
But since it has the same functionality available as lang qb, splitting the page maybe wouldn’t streamline things that much.
I don’t mind if it stays the way it is, particularly if the issue has been sitting in someone else’s backlog for 11 years!
Re: Wiki improvements
Does anyone object if I split the first example on https://freebasic.net/wiki/KeyPgOpNew into 2 examples?
The use of 'Scope / End Scope' might be a nice example for the use of 'Scope', but only confusing on the 'New' page.
BTW: The forum seems a bit broken at the moment here, I hope it is only temporary.
The use of 'Scope / End Scope' might be a nice example for the use of 'Scope', but only confusing on the 'New' page.
BTW: The forum seems a bit broken at the moment here, I hope it is only temporary.
Re: Wiki improvements
Or, in the example, just remove both scopes but use 2 different pointer names.
Re: Wiki improvements
I decide to split the example. This was more in line with the 3rd example (1st = new / single element, 2nd = new [], 1D-array, 3rd = new [], 2D-array).
The 2nd example is a bit boring, nothing was printed. I added "Done.", to give at least some feedback.
The 3rd example (untouched by me) is not for a beginner, with: Dim As UDT Ptr Ptr p = New UDT Ptr [4]
The 2nd example is a bit boring, nothing was printed. I added "Done.", to give at least some feedback.
The 3rd example (untouched by me) is not for a beginner, with: Dim As UDT Ptr Ptr p = New UDT Ptr [4]
Re: Wiki improvements
I just modified the second filename because 2 examples cannot have the same filename.
Fortunately, in the reference documentation there are not only examples for beginners!
Fortunately, in the reference documentation there are not only examples for beginners!
Who is online
Users browsing this forum: No registered users and 2 guests