Let me play devils advocate for a minute:
If we create a library with such a wiered API that we need another library
to make use of that libary easy - maybe we are abusing that libary or
we should reconsider its API?
This is one of the ocassions where I would love to use C++ and templates
in the
Correction:
On Thu, Nov 04, 2010 at 01:36:15AM +0900, Masao Uebayashi wrote:
I have found that XIP is very similar to AMAP_SHARED, at the point
where XIP supports write operation.
Imagine a FlashROM page is XIP'ed and shared as vnode by processes.
The user rewrite the firmware written onto
On Tue, Nov 02, 2010 at 02:08:13PM +0100, Joerg Sonnenberger wrote:
On Tue, Nov 02, 2010 at 01:35:10PM +0900, Masao Uebayashi wrote:
If a small program has both .data and .bss, and if .data is small,
I'd use .rodata and copy it to .bss explicitly, so that resulting
process allocates only
On Wed, Nov 03, 2010 at 09:28:11AM +0100, Martin Husemann wrote:
This is one of the ocassions where I would love to use C++ and templates
in the kernel ;-}
I think what you mean is that you'd like to have a language that has
some kind of sane parameterized types... :-/
--
David A. Holland
