I've been working on this for a few days, and finally have something good to show.
I started using CodeKeeper recently because it would use source replace to allow you to use both global variables, and that wonderful taping feature which would allow you to do use global variables and other non function related things in #include files. Unfortunately the editor isn't very stable, and it all of a sudden just stopped replacing things properly. I thought I must not be the only person to have experienced this problem, or if nobody else has then this at least gives you the opportunity to use globals and taping without having to deal with bugs.
The beauty of this is that it's a console application (yeah, I'm a C++ nub, it worked to my benefit anyway). Once I get command line compiling up and running you will be able to compile, run, and build your DBC programs from any text editor that allows you to run external exes or batch files.
My editor of choice from now on will be
Crimson Editor, and I have provided darkbasic syntax definition files for you to stick in your Crimson Editor install directory in the "spec" and "link" directories. Once I get command line arguments all done I'll also release a user tool you can load into the program with 4 options for compile, run, build debug, and build final.
The current version will read in your main source file, check for TAPE statements, and inject code from the files specified in your TAPE statements into your main source file exactly where you put the TAPE. The limit, of course, is that you can only tape from the main source file.
It will also convert GLOBAL statements into DIMs and change the variables in 0-element arrays DarkEdit style.
Syntax for globals is exactly like DarkEdit:
"GLOBAL myvar# : myvar#=4.5" == "DIM myvar#(0) : myvar#=4.5(0)"
Syntax for TAPES works exactly like #include, except you would of course use TAPE and the code is injected into the point at which you typed the TAPE statement in your main source file.
Downloads:
DSR.exe - This is the current version of Dark Source-Replace. It will prompt you to enter a file name, then perform all the checks and replacements I mentioned above and tell you what the file is called that it wrote to, it does not alter your code, just copies it.
Below are the darkbasic syntax definition files that I whipped up real quick for Crimson Editor. This allows Crimson Editor to do syntax highlighting for DB commands and will automatically detect if you are using DB based on the extension of the file.
Keywords-Goes in the Crimson Editorspec directory.
Specification-Goes in the Crimson Editorspec directory.
Specification-Goes in teh Crimson Editorlink directory.
Planned Features:
Run as a command line tool with arguments defining specific file information, exe destination, compile/run/build options
User tool to integrate into Crimson Editor
DBCompile.log output
Please let me know of any bugs you find, any features you want, any useful console output you'd like when you run the program, or any old c&c you may have.
I'm going to eat you!
