Re: [Dev-C++] Dev settings to remove @ symbol from dll exported functions - please, help!

[<or...@vp...>]

Hi!

Well, the topic diversed a bit from the original part. My fault again.
I have no trouble with "Borland" itself - more like Delphi, the 
language. I even used Borland some time ago. Their C++ compiler is free 
(not the IDE). So Borland is good. *Deplhi* is not.

But to turn back to the original part: I "think", that if someone uses 
OTHER tools than the GNU tools for creating an IDE for GCC, then it may 
not turn out good. I mean, try to write an IDE for Deplhi (more 
accurately: for the Borland tools), using GNU tools. You would end up 
with partial/wrong support for the Borland compiler.

So, I think the best would be to study hardly the GNU tools, and follow 
every change in it today, and make Dev-C++ up-to-date.
For the original part: I think instead of dllwrap, gcc and g++ -shared 
should be used.

About the IDE bugs: yes, it is quite a long time in development, and it 
is still beta. The bugs occured when I tried to compile bigger projects: 
the makefile is just not generated, then I get the exception window 
about "Invalid filename"s. But when I double-click the project file in 
Explorer, and Dev-C++ opens up, the SAME project compiles. Odd...

Other:
A problem with Dev-C++, is that the developers don't listen to the users 
at all. I have written a personal mail to one of the devs some time ago 
about giving support for use of environment variables (%ENV_VAR% or 
$(ENV_VAR)) at include and library dirs, but I haven't even got a 
response ever since. It would be way better, if the developers of 
Dev-C++ would listen, or at least, sometime read this list.

And last: I have been watching the mails' subjects on this list, and 
most are C/C++ questions. That is not a problem, and it is good in fact, 
because there are many talented C/C++ programmers here. BUT: whenever 
someone asks about Dev-C++, THE IDE ITSELF, he RARELY gets any sort of 
answer: not even like: "I cannot help, ask here...". This is not good. 
It seems, that everyone (the good C/C++ progammers here) get lost in the 
details: about whether this

#ifdef XXX
#define AAA
#endif

or this

#ifdef XXX
#  define AAA
#endif

is correct, and there are 20 mails arguing about this (it's just a 
sarcastic example).
So I think, the focus on this list should be more on Dev-C++, the IDE, 
and secondly on C/C++ (and thirdly on cars, and ONLY fourth about MFC :)

So, again, I have nothing against Borland. Their compilers are fine. I 
even used them. I just say... what I said above :)

--
Greetings,
   Balázs