EDIT Big Time:
Can I see how you do a PureBasic memory allocation? I want to see what you mean about this index variable thing...
I've been sitting here thinking about how to do a "create, resize, and free memory buffers" in C. I'm thinking that Vector Arrays are truely the way to go here. I'll try to knock something up here soon. Also, I would imagine the dll memory management would be faster than poking around with banks. Ofcoarse, I'm just imagining that at the moment.
When it comes down to doing things like BSP's and collision testing, I would rather see it done in C then seeing it written in Blitz. Mabie it's just a case of seeing to believe it in blitz for me to see a good speed performance in operations like that. Ofcoarse here, if something like that gets written in Blitz code, then like I said in my first post, I'll be glad to convert it to C/C++ code to see if it would be worthy that way.
I remmember someone writting a direct blitz userlib for the devIL library. I would take that route for including images/textures or I can knock up a C/C++ dll to manage it better if needed be. I still hadn't checked out OpenAL fully yet as in I don't know if it's possible to write a direct userlib to the OpenAL dll(s). I just want to make sure that either which way it's decided to store data that we can grab data directly from memory or from a pack file for any media. I don't want to see the "write to disk, load it, delete it, and so on.." hack.
I'll go ahead and ponder more on the significants of using a dll for memory manipulation of data.
"How much of this should be written in DLL's?" - I would agree to " as less as possible ". As this project being written for blitz, userlibs are part of the game. Make use of them. Any Dll's that get included into the project should definetly get it's source code included along with it being in compiled form so anybody can use it.
Oh, I'll have a second look at your new blitz "structure" method also to see if I can work the memory dll with it. It's a shame blitz doesn't support C-Style structures, eh?
Can I see how you do a PureBasic memory allocation? I want to see what you mean about this index variable thing...
I've been sitting here thinking about how to do a "create, resize, and free memory buffers" in C. I'm thinking that Vector Arrays are truely the way to go here. I'll try to knock something up here soon. Also, I would imagine the dll memory management would be faster than poking around with banks. Ofcoarse, I'm just imagining that at the moment.
When it comes down to doing things like BSP's and collision testing, I would rather see it done in C then seeing it written in Blitz. Mabie it's just a case of seeing to believe it in blitz for me to see a good speed performance in operations like that. Ofcoarse here, if something like that gets written in Blitz code, then like I said in my first post, I'll be glad to convert it to C/C++ code to see if it would be worthy that way.
I remmember someone writting a direct blitz userlib for the devIL library. I would take that route for including images/textures or I can knock up a C/C++ dll to manage it better if needed be. I still hadn't checked out OpenAL fully yet as in I don't know if it's possible to write a direct userlib to the OpenAL dll(s). I just want to make sure that either which way it's decided to store data that we can grab data directly from memory or from a pack file for any media. I don't want to see the "write to disk, load it, delete it, and so on.." hack.
I'll go ahead and ponder more on the significants of using a dll for memory manipulation of data.
"How much of this should be written in DLL's?" - I would agree to " as less as possible ". As this project being written for blitz, userlibs are part of the game. Make use of them. Any Dll's that get included into the project should definetly get it's source code included along with it being in compiled form so anybody can use it.
Oh, I'll have a second look at your new blitz "structure" method also to see if I can work the memory dll with it. It's a shame blitz doesn't support C-Style structures, eh?