Re: How to suggest edits to the manual?
- Posted by dcuny Feb 03, 2015
- 1295 views
Thanks for the detailed response!
But... As usual, I'm a bit confused. Isn't the text pulled from the include file source code?
I'll (eventually) get around to writing up the bitmap stuff. That's pretty straight forward. I'll probably also eventually adding some sort of pixel routine as well.
I've got a lot of issues with the writeup Pseudo Memory.
I assumed (based on the name) that it was somehow used to interface to C programs by providing "raw" memory access. All the routine names imply this: ram_space, malloc, free.
The documentation uses the terms RAM, heap and block to describe what the routines do:
- ram_space: "The (pseudo) RAM heap space"
- malloc: "Allocate a block of (pseudo) memory"
- free "Deallocate a block of (pseudo) memory"
Unfortunately, there is no RAM (not even pseudo), heap, or block.
This example certainly looks like it's allocating and freeing RAM, and "do more processing" gives no clue what sort of processing might be going on:
my_spot = malloc(1,0) ram_space[my_spot] = my_data -- . . . do some processing . . . free(my_spot)
Really, just about everything here should be renamed.
- David
