Re: Fullscreen application Specs

--- In [email protected], Ivan Warren <ivan@...> wrote:
>
> You might be willing to use C strings at some 
> point, but nothing 
> prohibits using those for lightweight stuff only.

Right. I remember having an argument with someone,
after showing them the assembler that was generated
by IBM C, and if they could fault it. And the
other guy insisted that they had a project at
some company and that C was x times slower than
assembler, and that this was "documented".

I asked him if they had used strcpy() in the code
instead of memcpy(), which is my guess at what
they had done wrong (basically got someone not
competent in C on S/3x0 to do the "trial"). He
didn't know, but insisted that that result was
real, and wouldn't countenance any fair test
where I got to write the C.
 
> I believe the idea is definitely the other around : The 
> "general" logic 
> is coded in C (array management, building the screen, 
> stuff like that) - 
> and the stuff that is intrinsic to the system is assembler 

Yes, that would be normal, but in his situation, he
had already stated he wasn't comfortable with a
non-C main, so I gave him the non-hosted solution.

> All current efforts around C on S/370 are limited to 
> GCC 3.3.4 - because 
> support for the old style - S/370 compatible - with OS like linkage 
> conventions were dropped after GCC 3.3.4.

I have a GCC 3.4.6 beta available in the os380
files area. It is even built using a standard
"configure", "make", and the JCL is generated
rather than handwritten.

BFN.  Paul.