|
Post by awsdert on Jun 3, 2010 23:45:16 GMT -5
How about starting an SVN, then those of us who don't care about stability can let you know what problems arise and if we have the knowledge try fixing it ourselves before posting our code fix in the forums. It will help you make the program open source and keep the program the way you want it (since you'll be the only one with upload permissions).
|
|
arek
New Member
Posts: 16
|
Post by arek on Jul 15, 2010 14:23:22 GMT -5
This has been asked for many times recently, and the answer is 'no'. Please read the "Known Requests" post linked at the top of every single page on this forum (you're asking for the source code/open source).
--Arek
|
|
|
Post by awsdert on Jul 23, 2010 1:04:11 GMT -5
How about a more advanced debugger that generates a text file of the code (with file name & line number of course) in current use and a list of the variables. (Obviously the emulator would have to pause play whilst doing this) at least then the problem could be found faster.
Edit:If the author doesn't like like the idea of it generating a copy of the current code but still likes the idea of generating something more tangle able than a simple dump then how about a simple table of file names, line numbers, variables & value of those variables. E.g. // at start of function #ifd DEBUG dbgrec[FUNCNO] = "file.cpp;56;none;NULL;"; if (pause = false) { #endif // code with more #ifd DEBUG dbgrec[FUNCNO] = ""; #endif // at end of function #ifd DEBUG } else { dbglog << dbgrec[FUNCNO]; } #endif
|
|