¿ªÔÆÌåÓý

Re: gcc vm370 lseek


 

On Mon, 2021-01-11 at 12:43 -0800, carlos feldman wrote:
That's why I like PL/I , the language includes I/O. C, sometimes can
be very limitative, since lot of functions are not implemented the
same way, And you have to write your own implementation. for instance
atoi(), something basic if you are wirking with user interfases. In
PL/I you write number=string; and you only get a compiler warning
I do a lot of embedded work and *not* having/needing a full C runtime
allows for writing the applications/OS/RTOS in an efficient manner.

In many cases I compile my C code with --no-stdlib and the like because
I don't need/want a lot of the C run-time. For example, in one case I
hand wrote a 64-bit divide by 1000 function because that was the only
use of the entire 64-bit math library on a 32-bit CPU. It saved almost
1KB of code (and was significantly faster as well). You might say a
1KB savings isn't alot but what I was doing, I only had 128KB for the
entire application and RTOS.

TTFN - Guy

Join [email protected] to automatically receive all group messages.