plex86-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: Re: [Plex86-devel] Release Schedule


From: Eric Laberge
Subject: Re: Fwd: Re: [Plex86-devel] Release Schedule
Date: Thu, 20 Jun 2002 14:35:32 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605

When I said I was looking to a COM-like design, I was mainly referring to the idea of having instanciable components and standard and compatible interfaces. My prototype implementation is very clean and completely usable. And it is 100% standard C. You can see it in any way, but any plugin structure can only be done with these elements. I only suggest we define a standard, non-bloated and portable structure. The current one is filled with legacy stuff, and undocumented, and [insert evil attribute here].

You mentionned guile, can you elaborate on how it can be used?

By referring to GUSS, do you mean sharing emulated devices? From what I see, it seems like a generic Bochs.

BTW, I completely agree we should rewrite at least the Bochs plugin from scratch.

EL

Jeroen Dekkers wrote:

IMHO we should write something from scratch:
http://savannah.gnu.org/projects/guss. There is already code for
powerpc which is working a little bit. Note that GUSS is made for OS
development, not for running windows, but that doesn't mean that it
will be impossible to run windows.

And COM really sucks, you should avoid it. I've seen it in OSKit, it
just sucks for the C language. You should use a CORBA IDL compiler if
you want something like COM.

BTW, I already have a working new config file format, so don't bother with
this one.

IMHO guile is the perfect system for configuration.

Jeroen Dekkers






reply via email to

[Prev in Thread] Current Thread [Next in Thread]