[coyotos-dev] Executable format for Coyotos

[Pierre THIERRY]

Scribit Jonathan S. Shapiro dies 04/03/2007 hora 17:25:
> I think you don't understand how the bootstrap works.

Probably. Fortunately I showed it.

> It isn't the constructor's job to fabricate a program from a binary
> image. That is the job of mkimage.

Say I have a running Coyotos system. On this system, I have a working
BitC compiler, or Common Lisp compiler. I write a program, and make an
executable of it for other users to be able to use it.

I thought that would involve creating a binary file and sealing a
constructor with at least authority to read that file. And that when
asked to instantiate my program, the constructor, from data in the
binary file, would make a process of it.

Much a when the loader in a Unix system creates a process from a *COFF
or ELF file. Except that because you aren't forced to have a single
constructor in Coyotos, you could as well use a different binary format
in different cases.

Where am I wrong?

> We're in the process of putting together some tutorial examples for a
> client.

Great.

Curiously,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.coyotos.org/pipermail/coyotos-dev/attachments/20070304/8a704bc2/attachment.bin