PellesC

[airr]

Thanks, MrB and Vortex!

AIR.

[Vortex]

Hello airr,

I would also recommend you the other tool of Pelle, Poasm - the assembler, Polink - the linker, Porc - the resource compiler, Polib - the library manager are very goo utilities compatible with the MS VC toolset.

[MrBcx]

Pelles is rock solid and a joy to use. 

The only thing I ( and others ) would advise is to stay away from its optimization options.
Optimizing for speed can be particularly troublesome, so don't do that.  If you choose to
optimize for speed, Pelles can be overly aggressive which can ( and probably will ) create
some hard-to-track-down bugs for you.  So, don't.

Pelle's IDE is great for building or editing dialogs and resources.  It generates very good
code, not quite as fast as MSVC but definitely better than Mingw.  And it is a pretty quick
compiler at doing its job, whereas some compilers come with frequent coffee breaks.  It's
a great tool to have in your toolbox.  It's been in mine for as long as BCX has been around.

[airr]

Cross-Platform considerations aside, what are your feelings regarding PellesC?

I'm a long time GCC user.  Been using it on Linux, macOS, and Windows, but I've really enjoyed coding in PellesC lately.

I like how strict Pelles is; things I could get away with using GCC simply don't fly on Pelles.

An example is Nested Functions.  TBH, I didn't even know you could do that using GCC; apparently it has a non-standard extension baked in that allows you to define and code functions INSIDE of a function.  As to why someone would want to do that, I have no idea.

Anyway, my big question:  Is Pelles production-ready, in the sense of stability/compliance/etc?

Thanks!

AIR.