@fxm:
Is this statement on https://www.freebasic.net/wiki/TutIntroArrays correct?
"Static arrays, the arrays described above, are kept on the heap, but dynamic arrays are allocated from the computer's pool of memory. The compiler dynamically allocates memory for the array based on the requested dimensions of the array."
I thought incorrect, but I may have misunderstood the 'heap'.
Wiki improvements
Re: Wiki improvements
In the context of this sentence, I think that 'static arrays' means 'fixed-length arrays' and therefore that this beginning of the sentence is wrong.
I simply propose to delete the beginning of the sentence:
I simply propose to delete the beginning of the sentence:
or correct it:Dynamic arrays are allocated from the computer's pool of memory. The compiler dynamically allocates memory for the array based on the requested dimensions of the array.
Static (fixed-length) arrays, the arrays described above, are kept either in static storage or on the program stack, but dynamic arrays are allocated from the computer's pool of memory. The compiler dynamically allocates memory for the array based on the requested dimensions of the array.
Last edited by fxm on Jan 24, 2025 6:08, edited 1 time in total.
Reason: Complemented post.
Reason: Complemented post.
Re: Wiki improvements
The first (with less information) seems better to me.
In both suggestions the reference to heap is gone, but in the second 'static storage or program stack' is now mentioned which is confusing if we don't explain the difference between these 2 concepts.
Maybe add a link to https://www.freebasic.net/wiki/ProPgDynamicMemory where this is better explained?
In both suggestions the reference to heap is gone, but in the second 'static storage or program stack' is now mentioned which is confusing if we don't explain the difference between these 2 concepts.
Maybe add a link to https://www.freebasic.net/wiki/ProPgDynamicMemory where this is better explained?
Re: Wiki improvements
Retained sentence:
Documentation updated:
TutIntroArrays → fxm [rewording]
Dynamic arrays are allocated from the computer's pool of memory called heap. The compiler dynamically allocates memory for the array based on the requested dimensions of the array.
Documentation updated:
TutIntroArrays → fxm [rewording]
Re: Wiki improvements
Hello,
I'm a completely blind FreeBASIC programmer, and I prefer reading the documentation in the compiled CHM format. However, when I do this, there are no spaces between keywords, so something like Dim Test As String is read as DimTestAsString by my screen reader, and when I go character-by-character there are no spaces like there would be in the compiled code. Is it possible for this to be fixed?
You can notice this behavior yourself by selecting the text with shift+arrow keys and copying it into notepad.
Thanks!
I'm a completely blind FreeBASIC programmer, and I prefer reading the documentation in the compiled CHM format. However, when I do this, there are no spaces between keywords, so something like Dim Test As String is read as DimTestAsString by my screen reader, and when I go character-by-character there are no spaces like there would be in the compiled code. Is it possible for this to be fixed?
You can notice this behavior yourself by selecting the text with shift+arrow keys and copying it into notepad.
Thanks!
Re: Wiki improvements
Maybe a problem with just Linux?
-
- Posts: 21
- Joined: Jun 09, 2024 18:26
Re: Wiki improvements
Maybe you could provide more information in your post.Quin wrote: ↑Mar 12, 2025 22:04 Hello,
I'm a completely blind FreeBASIC programmer, and I prefer reading the documentation in the compiled CHM format. However, when I do this, there are no spaces between keywords, so something like Dim Test As String is read as DimTestAsString by my screen reader, and when I go character-by-character there are no spaces like there would be in the compiled code. Is it possible for this to be fixed?
You can notice this behavior yourself by selecting the text with shift+arrow keys and copying it into notepad.
Thanks!
OS?
Version?
Architecture?
How you are currently viewing it i.e. OS built-in or third party software?
and maybe a reference to the page you are referring to.
Using Debian 11 (Bullseye):
I can view the CHM manual perfectly using either xChm (Debian repo package) or via wine hh.exe <.chm file>
Re: Wiki improvements
Sorry, I should've been more specific. I'm on Windows, using the free NVDA screen reader from nvaccess.org, reading the provided CHM file in Microsoft's built-in CHM viewer. I imagine it looks fine visually, my assumption is it's either some weird unicode character or some odd CSS styling inside code blocks.
Thanks!
Thanks!
-
- Posts: 21
- Joined: Jun 09, 2024 18:26
Re: Wiki improvements
No problem.Quin wrote: ↑Mar 13, 2025 13:17 Sorry, I should've been more specific. I'm on Windows, using the free NVDA screen reader from nvaccess.org, reading the provided CHM file in Microsoft's built-in CHM viewer. I imagine it looks fine visually, my assumption is it's either some weird unicode character or some odd CSS styling inside code blocks.
Thanks!
As I'm not a Windows user (not since XP) I'm really not able to assist further, maybe a Windows guru will be along soon?
Good luck.