This may be is a little off-topic qustion, but Im sure a lot of you are very
experienced programers, so may be you can give me a tip or just a little
orientation.
I want to know things, like for example, how much memory will my aplication
will use, how to debug my apps, how to write my code efficiently, etc, etc.
I have been takeing a look on google about GDB, and also i readed the man
pages from my bsd box about it. But may be theres some place, or some
docuementation you know that may be good for me to read and understand a
little more about. I dont pretend to be a god programer, just a good
aprentice… and i really hate to know for example, how to make a surface
when i dont know exacly how much memory im using, how is that surface
created, what is the internal process, etc… I couldnt find information
about internal functionality of SDL / Video, may be thats not the
information a user will want to know, but well… may be it can help to know
how things work.
Thanks for any help, and sorry for this little “off-topic” question
really hate to know for example, how to make a surface when i dont
know exacly how much memory im using, how is that surface created,
what is the internal process, etc… I couldnt find information
about internal functionality of SDL / Video, may be thats not the
information a user will want to know, but well… may be it can
help to know how things work.
I don’t think there is much documentation on the inner workings of
SDL, but why not just read the source? Use some search tool (like
’grep’ on Un*x) on the source tree to find the entry points quickly,
and then follow the code from there.
Another way is to do it “live” with the debugger in step mode. (Just
don’t do it in fullscreen mode! Make sure you have the full SDL
source where the debugger can find it, and an SDL binary with debug
info.
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`-----------------------------------> http://audiality.org -’
— http://olofson.net — http://www.reologica.se —On Tuesday 03 June 2003 23.55, eDU! wrote:
----- Original Message -----
From: david@olofson.net (David Olofson)
To:
Sent: Tuesday, June 03, 2003 7:27 PM
Subject: Re: [SDL] Learning a little more
really hate to know for example, how to make a surface when i dont
know exacly how much memory im using, how is that surface created,
what is the internal process, etc… I couldnt find information
about internal functionality of SDL / Video, may be thats not the
information a user will want to know, but well… may be it can
help to know how things work.
I don’t think there is much documentation on the inner workings of
SDL, but why not just read the source? Use some search tool (like
’grep’ on Un*x) on the source tree to find the entry points quickly,
and then follow the code from there.
Besides grep, which must have some additional help from a little pipe
magic to span a directory hierarchy, you could probably benefit from a
little tool called cscope.
Cscope creates a database of all the symbols in the code tree and you
can jump around in the code easily, e.g. you encounter a usage of an
unfamiliar struct, to bring up the declaration of that struct is a
piece of cake. I used this tool with Workshop, Sun’s compiler suite,
but I’ve noticed that it gone open source here: http://cscope.sourceforge.net
For lucky(?) users of either visual studio or apple’s project builder
it’s an already built in feature
Good luck!
/jOn onsdag, jun 4, 2003, at 00:27 Europe/Stockholm, David Olofson wrote:
----- Original Message -----
From: jt@dd.chalmers.se (Jim Tilander)
To:
Sent: Wednesday, June 04, 2003 6:39 PM
Subject: Re: [SDL] Learning a little more
On onsdag, jun 4, 2003, at 00:27 Europe/Stockholm, David Olofson wrote:
On Tuesday 03 June 2003 23.55, eDU! wrote:
[…]
really hate to know for example, how to make a surface when i dont
know exacly how much memory im using, how is that surface created,
what is the internal process, etc… I couldnt find information
about internal functionality of SDL / Video, may be thats not the
information a user will want to know, but well… may be it can
help to know how things work.
I don’t think there is much documentation on the inner workings of
SDL, but why not just read the source? Use some search tool (like
’grep’ on Un*x) on the source tree to find the entry points quickly,
and then follow the code from there.
Besides grep, which must have some additional help from a little pipe
magic to span a directory hierarchy, you could probably benefit from a
little tool called cscope.
Cscope creates a database of all the symbols in the code tree and you
can jump around in the code easily, e.g. you encounter a usage of an
unfamiliar struct, to bring up the declaration of that struct is a
piece of cake. I used this tool with Workshop, Sun’s compiler suite,
but I’ve noticed that it gone open source here: http://cscope.sourceforge.net
For lucky(?) users of either visual studio or apple’s project builder
it’s an already built in feature
Make sure you have the full SDL