Version 10.00 (RC1) is now available

[Pelle]

Pelles C version 10.00 (Release Candidate #1) is now available for download:
http://www.smorgasbordet.com/pellesc/download.htm

Major changes:
http://www.smorgasbordet.com/pellesc/changes_900_1000.htm

/Pelle

[bitcoin]

This is very good news. Thank you Pelle!
Will be use it.

[dstritt]

I don't know if I am missing something but the download link posted just takes me to the older 9.0 downloads.

[MrBcx]

I don't know if I am missing something but the download link posted just takes me to the older 9.0 downloads.

http://www.smorgasbordet.com/pellesc/1000/setup.exe

[Grincheux]

Thank You Mr Pelle.
That's a good news.
I installed the new version, I don't see any change except the dialog boxes for the project options.
They were better in version 9.0.
I hoped that the new version would bring other things. I am disapointed.


Thanks for all you do for giving us the best compiler in the Windows World.

[MrBcx]

Thank you Pelle !

Your compiler has long been my favorite -- fast compiles, competitive performance, and thoughtful improvements.

I spent time today testing and everything is looking great.

Your tools provide Winapi developers with a sane, comfortable, and reliable alternative to Visual Studio.

[TimoVJL]

Thanks Pelle.

[jullien]

Many thanks for working to a new version.
The RC1 dropped Windows _snprintf_ and _TRUNCATE support. I now get for example:

stacks.c(118): warning #2018: Undeclared function '_snprintf_s' (did you mean: snprintf?); assuming 'extern' returning 'int'.
stacks.c(118): error #2048: Undeclared identifier '_TRUNCATE' (did you mean: ?).

See: https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/snprintf-s-snprintf-s-l-snwprintf-s-snwprintf-s-l?view=vs-2019

[AlexN]

  Great Pelle!

But where can I now select to get a 32 bit or a 64 bit target?

[briman]

Although I'm still trying to learn C I have downloaded and installed V10 Candidate #1 to help kick the tires 

Thanks for keeping Pelles C alive

[frankie]

  Thanks
I have same question as Alex: where can we select 32/64bits? 

[Pelle]

bitcoin, MrBcx, TimoVJL, briman:
Thank you!

AlexN, frankie:
Thank you! I moved 32/64-bit selection to Project "Properties" (right-click a project node f.e.): easier for me to do all the changes in one place (old code was an afterthought, and not a very good one).

jullien:
I have tried to follow "Annex K: Bounds-checking interfaces" - an optional part of the C11 and C17 standard (but possibly removed from the C2X standard). I think this proposal originally may have come from Microsoft, but Microsoft and the standard text have never been in total sync. Anyway, I rather stick to standard C (even optional parts) rather than this weeks Microsoft "standard"...

[AlexN]

AlexN, frankie:
Thank you! I moved 32/64-bit selection to Project "Properties" (right-click a project node f.e.): easier for me to do all the changes in one place (old code was an afterthought, and not a very good one).

Thank you! I found it, but I don't expect it there.

[frankie]

AlexN, frankie:
Thank you! I moved 32/64-bit selection to Project "Properties" (right-click a project node f.e.): easier for me to do all the changes in one place (old code was an afterthought, and not a very good one).

Got it thanks.
But on my system switching between 32 and 64bits the libraries path is changed in a wrong way: setting "lib\Win" for 64 bits compiles and "lib\Win64" for 32bits code. Manually fixing the libraries path in the project options->macro, compilation completes successfully.
Is it my problem or is a small IDE bug?

[Pelle]

Thank you! I found it, but I don't expect it there.

Good... and, I guess, ... SURPRISE!