'D' source files are ALWAYS UTF-8. I couldn't find any way to convert my source code file into UTF-8 in Code::Blocks (only converted by external tools). Maybe it is the time to let programmers to choose the source file encodings? Moreover, when handling 'D' projects it is natural to set UTF-8 encoding for the source files by default.
What's wrong with "Settings->Editor->Default encoding"?
Build and Code::Blocks overlap too much, build + D is just like make + C++/C. If you want to use build you have to invoke it just like you would make.
Tell me, why I cannot convert files (source code or whatever) to any other encodings just within CB. I care this because the English language is not my native one and I make my comments and string constants in my native language. Why not to do just like Ultimate++ IDE allows you to do that?
It's so natural tool and not so hard to implement? So why?????
Thanks for your explaination. But let me disagree with you. It is my responsibility to tune the build tool in a such a way that it works right for me. The only responsibility for CB is to call it and to pass the needed arguments to it. That's all.
<Option compilerVar="CPP" />
<Option compiler="gcc" use="1" buildCommand="gdc $options $includes -c $file -o $object" />
Offtopic: Have they renamed build to dbuild.
Oh, no, another one...
Look Ptomaine, if you like [whatever_ide_goes_here] better, please, just use it.
QuoteIt's so natural tool and not so hard to implement? So why?????
Because noone has sent a patch for it. It's that simple.
Tell me, why I cannot convert files (source code or whatever) to any other encodings just within CB.Is it, because you didn't try Edit->File encoding?
Tell me, why I cannot convert files (source code or whatever) to any other encodings just within CB.Is it, because you didn't try Edit->File encoding?
Oh, no, another one...
Look Ptomaine, if you like [whatever_ide_goes_here] better, please, just use it.
You right! I use it for tasks I think it works better for me. And this IS NOT the reason for you to be aggressive to US. Usually, good companies pay very close attension to their customer feedbacks. Why you try to argue to me while I'm trying to help imporoving CB? I do not understand.
QuoteIt's so natural tool and not so hard to implement? So why?????
Because noone has sent a patch for it. It's that simple.
It's not that simple at all. Read the previous posts.
What does it take that you accept a patch? How much time do you need to include it?
Will C::B be always targeted at C++ only?
Index: src/sdk/compiler.h
===================================================================
--- src/sdk/compiler.h (revision 2971)
+++ src/sdk/compiler.h (arbetskopia)
@@ -130,6 +130,7 @@
{
wxString C; // C compiler
wxString CPP; // C++ compiler
+ wxString D; // D compiler
wxString LD; // dynamic libs linker
wxString LIB; // static libs linker
wxString WINDRES; // resource compiler
So it would be OK to work on a patch that adds D as a new language "proper",
instead of adding DMD and GDC as new (C/C++) compilers as currently used ?