[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] fdevopen() uses calloc?
From: |
Rod Moffitt |
Subject: |
Re: [avr-gcc-list] fdevopen() uses calloc? |
Date: |
Thu, 22 Jan 2004 00:54:42 -0500 (EST) |
I entirely agree. It would be great if fdevopen could be stripped down (to
a malloc-less version) when libc is being built, akin to what is done
with printf with the floating point support.
- Rod
--
___ ____ ___ _ ___
Rod Moffitt / _ \/ __ \/ _ \ (_)__ / _/__
http://rod.info / , _/ /_/ / // / / / _ \/ _/ _ \
address@hidden /_/|_|\____/____(*)_/_//_/_/ \___/
=======================================================
~ Where loved ones are remembered http://memoriam.org ~
On Wed, 21 Jan 2004, Joerg Wunsch wrote:
> "J.C. Wren" <address@hidden> wrote:
>
> > What about something like this? Create fdevopens(), which is
> > basically identical to fdevopen(), except uses an internal static
> > __file instance.
>
> I rather thought about the same kind of linker trickery as it is done
> for the decision between standard, full (floating-point), and minimal
> printf/scanf versions. That way, the source code would always use
> fdevopen(), but the linker configuration decides which implementation
> of fdevopen() to use.
>
> --
> J"org Wunsch Unix support engineer
> address@hidden http://www.interface-systems.de/~j/
>
> _______________________________________________
> avr-gcc-list mailing list
> address@hidden
> http://www.avr1.org/mailman/listinfo/avr-gcc-list
>
Re: [avr-gcc-list] power on mega 103, nurdin, 2004/01/23