ORCA/C 2.2.0 B7

[Stephen Heumann]

Hi folks,

I've just released ORCA/C 2.2.0 B7. The full source code is available
on GitHub, and a binary update package is on the releases page:

https://github.com/byteworksinc/ORCA-C/releases/tag/orcac-220b7

This is the latest version of ORCA/C, the C compiler for the Apple
IIGS. In addition to various bug fixes, this release includes a number
of new features:

* Support for new language features from C99 and C11
- Designated initializers
- Anonymous structures and unions
- `_Pragma` preprocessing operator
- `__STDC_VERSION__` macro
- C99-compliant `inline` semantics (but no actual inlining)
- C11-compliant `_Thread_local` specifier (but no multithreading)
* Other compiler features
- C standard selection, including strict conformance modes
- Debugging option to detect illegal use of null pointers
- Lint check for unused variables
- Lint check for implicit conversions that change constant values
- Small improvements to compiler performance and generated code
* New library features
- Optional support for time zone handling using the Time Tool
- `timespec_get` function
- `erf`, `erfc`, `fma`, and `tgamma` math functions
* Auto-segmenting linker

ORCA/C 2.2.0 B7 now supports nearly all the features required by C17,
apart from wide character support and some floating-point library
features.

Note that this update must be applied on top of an existing copy of
ORCA/C 2.1 or later. If you don't already have that, it's available as
part of the Opus ][ collection sold by Juiced.GS.

There is also a corresponding update to the GNO-specific version of
ORCALib, which you should get if you are using ORCA/C under GNO:

https://github.com/byteworksinc/ORCALib/releases/tag/gno-orcalib-220b7

[Antoine Vignau]

When will you call it 2.2.1 or 2.3?
av

[Pierre Durant]

Le samedi 8 avril 2023 à 21:41:51 UTC+2, Antoine Vignau a écrit :
> When will you call it 2.2.1 or 2.3?
> av

I updated but now REZ compilation is not possible anymore ?????

[stephen...@gmail.com]

The update should not have any effect on Rez. What error are you seeing?

--
Stephen Heumann

[Pierre Durant]

for example I open the example "Prob.14.1.rez" of the Toolbox c examples provided which is clearly identified as a REZ in menu Languages
I "compile to disk"
and I recieve an error box "a compiler is not available for this language"

[Pierre Durant]

Sorry Stephen, I made an error during the installation of the B7 version ! Now it's OK , no more issue to compile a REZ file ! :-)

But I want to take this opportunity to ask you a little question for which I didn't find the answer in the documentation.
So, I have a Desktop App with multiple .cc and .h files.
I succeed to write a make file which compile and link all the sources.
The compile/link works fine and I'm able to execute the app without error.
But.... How to run it in debug mode ???
If I open the main source and push on "trace" for example it try to link again this souce but it fails like it was trying to link the app with the main source only.... :-/
So, how to debug an app for which you have multiple .cc/h modules ???

thanks :-)

Pierre

[stephen...@gmail.com]

On Thursday, April 27, 2023 at 12:18:23 PM UTC-5, Pierre Durant wrote:

> But I want to take this opportunity to ask you a little question for which I didn't find the answer in the documentation.
> So, I have a Desktop App with multiple .cc and .h files.
> I succeed to write a make file which compile and link all the sources.
> The compile/link works fine and I'm able to execute the app without error.
> But.... How to run it in debug mode ???
> If I open the main source and push on "trace" for example it try to link again this souce but it fails like it was trying to link the app with the main source only.... :-/
> So, how to debug an app for which you have multiple .cc/h modules ???

If you want to debug a program built using a script, you need to make sure it is built with debug code enabled, either by using the +D flag on the compile commands in the script or by using #pragma debug in the code.

Then you can execute it using the Run->Execute... menu option to debug it. The debug mode to use can be set under Run->Execute Options...

--
Stephen

[Pierre Durant]

The option +D was already specified in my make file. The "run-> execute options" is set to "trace".
I can use "run->execute"... but don't see any "menu option" ? I can switch between the app and orca but no window of my source appear even if I set a breakpoint before the loop of the app...

[stephen...@gmail.com]

On Thursday, April 27, 2023 at 2:35:31 PM UTC-5, Pierre Durant wrote:

> The option +D was already specified in my make file. The "run-> execute options" is set to "trace".
> I can use "run->execute"... but don't see any "menu option" ? I can switch between the app and orca but no window of my source appear even if I set a breakpoint before the loop of the app...

You need to open windows with your source files manually before you run the program with Run->Execute.... If you set the breakpoints before compiling the code, I believe it should stop at the first breakpoint, but if you are having trouble you might want to set it to Step mode, which should let you just step through starting from the first statement in your program.

--
Stephen

[Pierre Durant]

When I do that, I come to a "blue screen of death".....

[Pierre Durant]

UPDATE: it's OK now ! The problem came from the bad conversion of the source text from windows to prodos ! Now I use CiderPress and the conversion is correct ! Interesting to know that a bad text format can have an impact on the debug process !

Thanks again Stephen for all your work !!! :-) It's great to have an C compiler up-to-date on the II GS ! :-)