ImageCraft Next-Gen IDE
ImageCraft
Posts: 348
For people interested in our next-gen IDE development, you may be interested in reading our latest blog entry: http://imagecraft.wordpress.com/2009/10/20/next-gen-ide-codeblocks-pre-alpha/
For the inevitable question of "when will it be available for ICC for Propeller," we are gauging the Prop II progress and will mesh the next-gen release with it. We also expect to add a lot more optimizations for the V8 release.
// richard
For the inevitable question of "when will it be available for ICC for Propeller," we are gauging the Prop II progress and will mesh the next-gen release with it. We also expect to add a lot more optimizations for the V8 release.
// richard
Comments
Thanks for posting and keeping us updated! Exciting stuff.
James
"Delphi 6 Source code of Dev-C++/..." Um, no thanks
C::B will allow us to move to OSX, Linux etc. The compiler themselves can be ported easily already.
Jack
Jonathan
(The only thing I really miss is integrated CVS / SVN / HG integration, but C::B has a nice plug-in architecture so that might arrive eventually, and using Tortoise* isn't difficult at all.)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
lonesock
Piranha are people too.
We *might* add something like: "Automatically install Tortoise SVN" type of command. We will see...
// richard
I do have other more inevitable questions:
* When will you update the zip to download to include the more current help-files found somewere else on your site?
* When will you remove the bug that the linker links the float-lib to the binary, even if no floats are used?
* When will you spend the 30 minutes to change from the ridiculous "compile for debug" when there is no debugger?
* When will you remove the useless MOV R15, R15?
* When will you remove the useless ADD TEMP0, #0?
* When will you no longer link unused code from user-libraries?
It's 3 months minus a few days that I reported those bugs to you. Or do we have to wait 'till the Prop II?
Nick
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Never use force, just go for a bigger hammer!
The DIY Digital-Readout for mills, lathes etc.:
YADRO
All but the last one is relatively easy. However, we do have a priority list. One of which is that we are replacing the Propeller asm/linker.
I know that not linking unused code requires a multi-pass linker (that would also serve all other compilers, I assume). And this certainly won't be a one-day-job!
That point would be relaxed a bit by the '@fileName' for defines I suggested to you. This could substitute the tiny entry-box for the defines and read a C-syntax file that is project related and has a list of #defines to #undef unused code in user-libs or to configure (size of buffers, functionality etc.) those libs.
Nick
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Never use force, just go for a bigger hammer!
The DIY Digital-Readout for mills, lathes etc.:
YADRO
For the C Preprocessor, we are adding the -inc:<file> switch which will act as if you have done a
#include <file>
in your source. Then you can have anything C preprcoessor items in there, including #define etc.
However, since we are moving ASAP to C::B, I hesitate to add code to the existing IDE, except to fix bugs. We shall see. There are only 26 hours in a day
Leon
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Amateur radio callsign: G1HSM
Suzuki SV1000S motorcycle
http://www.codeblocks.org/
Nick
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Never use force, just go for a bigger hammer!
The DIY Digital-Readout for mills, lathes etc.:
YADRO
Leon
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Amateur radio callsign: G1HSM
Suzuki SV1000S motorcycle