[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> From the mail and conversations I have had, DevC++ is
> very unstable and unhelpful and doesn't do it's job
> that well and confuses people to death.
I've never tried DevC++ (only used VIDE from the very beginning), so I can't
really compare but I think the idea of bundling the compiler with the IDE is
a Bad Idea (tm), especially given that GCC is primarily a command line
compiler. According to the many messages on [AL], it indeed seems to be
confusing for lots of people (although the clarifications by Bob and Henrik
seems to have made things a little smoother).
> I just tried VIDE (I had an old version 1.15) and it was really
> easy to setup and use, didn't crash, used makefiles
> properly and was generally super :)
Really never crashed ? I can think of a very common situation where it
crashes 90% of the time for me (v1.15 and v1.22).
> How about changing the 'default' mingw IDE?
There's not really such a thing as the 'default' IDE. But I agree that the
sentence "This is the prefered choice for those who like to work in a
graphical development environment." is a little oriented ;-)
> Not if you are a new user reading docs/readmgw.txt, a
> lot of people think DevC++ is the compiler ;)
Yet docs/build/mingw32.txt is clear: "You have four choices when it comes to
installing MingW32 and Allegro on your computer", followed by 4 clearly
distinguished cases.
But I agree that VIDE ought to be mentioned and the oriented sentence
removed. Do you want to post a patch against docs/build/mingw32.txt ?
--
Eric Botcazou
ebotcazou@xxxxxxxxxx