I'm a professional programmer now and have recently gone back to the QuakeC code I wrote the better part of a decade ago in college.
The vision I have is a server that tracks a whole bunch of data on players as they play. The events are already trapped nicely in the code, so it is just a matter of creating a call to store the data inside the existing functions.
It is the storage of the data that seems to be the pain in my ass at the moment. I have a few ideas, but have so far found nothing for any of this.
1) The best method would be if I could use ADO and shove all the info into a database directly.
2) If I could write to a flat file I could whip up a simple external program to parse the file and shove it in the database indirectly.
3) If I could reference an external dll I could put the ADO functionality in there and just call it from the QuakeC code.
4) If I could shell an external program (using the info I want to store as a command line argument) from within the QuakeC code I could store the data.
Thusfar I have not discovered any way to do any of these. In fact, I keep finding documentation explicitly stating I CAN'T do some of this stuff (like the inability to write files was an intentional omission in QuakeC).
I'm hoping somebody here may either have a partial or whole solution to this.
--
Broc
The vision I have is a server that tracks a whole bunch of data on players as they play. The events are already trapped nicely in the code, so it is just a matter of creating a call to store the data inside the existing functions.
It is the storage of the data that seems to be the pain in my ass at the moment. I have a few ideas, but have so far found nothing for any of this.
1) The best method would be if I could use ADO and shove all the info into a database directly.
2) If I could write to a flat file I could whip up a simple external program to parse the file and shove it in the database indirectly.
3) If I could reference an external dll I could put the ADO functionality in there and just call it from the QuakeC code.
4) If I could shell an external program (using the info I want to store as a command line argument) from within the QuakeC code I could store the data.
Thusfar I have not discovered any way to do any of these. In fact, I keep finding documentation explicitly stating I CAN'T do some of this stuff (like the inability to write files was an intentional omission in QuakeC).
I'm hoping somebody here may either have a partial or whole solution to this.
--
Broc
Comment