• Messages sorted by: [ date ][ thread ][ subject ][ author ] [ Next ]
• [ Previous ] In reply to: Marc Stiegler

This is a multi-part message in MIME format.

------=_NextPart_000_001F_01BEF394.07CAE780 Content-Type: text/plain;

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Marc! By the way, thanks for Earthweb--I greatly enjoyed it, and of = course I'm using it to answer the question "Why do we need = capability-based security?" whenever I'm asked!

-----Original Message-----
From: Marc Stiegler <marcs@skyhunter.com> To: Paul Snively <psnively@earthlink.net>; e-lang@eros-os.org =
<e-lang@eros-os.org>

Date: Monday, August 30, 1999 6:37 PM Subject: Re: Build Problems Resolved =20
=20
>'Tis for markm to consider; goodness knows, markm's psychological = >profile makes him inclined to do total rewrites as often as possible, = at >the earliest possible moment :-)

=20
I guess I tend to side with markm, then, given how much awful code = that's come into being through accretion I've had to deal with...

=20

    >However, the following points are true:
    >=20
    >--the OROMatcher is not  part of the problem with IBM VA jvm or the =
>other jvms or JITS. These problems occur in implementations of E that =

=20
Got it. I'll let my question stand, however, due to OROMatcher not = being open source.

=20
--markm has a design for byte code compilation compatible with the = existing system=20

=20
That's also good news, but does it get us closer to accomplishing = other goals at the same time? My point from my original e-mail on the = subject was that a rewrite might afford us the opportunity to unify what = currently would need to be disparate approaches to things, e.g. = bytecode-generation would be one thing and getting on EROS would be = another, whereas a rewrite of the interpreter/compiler could get us = closer to both by accomodating the notion of multiple targets, where = Java bytecodes were one such target and native Pentium-family code with = an appropriate native runtime for, e.g. EROS would be another.

=20
>--there is work ongoing to build a persistence system within the = current >design (at least I think it is ongoing :-).

=20
I'd be most interested in hearing more about this. The last I heard, = ColdStore was under consideration for integration, but it's hard to see = how this would happen in Java without JNI and lots of wrappers--apart = from reimplementing the JVM atop ColdStore, which is what the ColdStore = folks would seem to prefer anyway. But once again, if your'e going to do = that, targeting EROS seems no harder.

=20
>Many of us are interested in E on Eros, the holdup there is getting = a jvm >on Eros.

=20
Once again, I wasn't thinking of running E in Java on EROS; I was = thinking of a native port with a native runtime.

=20
Does this make any more sense?
=20
>--marcs
=20
Thanks!
=20
Paul=20

        -----Original Message-----
        From: Paul Snively <psnively@earthlink.net>
        To: Marc Stiegler <marcs@skyhunter.com>; e-lang@eros-os.org =


<e-lang@eros-os.org>

        Date: Monday, August 30, 1999 5:00 PM
        Subject: Re: Build Problems Resolved
       =20
       =20
        Folks,
        =20
        I have to ask this; please forgive me.
        =20
        Is it time to rewrite E?
        =20
        It seems to me that there are several goals that have already =

        =20
        1) Reintroducing persistence--of particular significance, =
perhaps, now that ColdStore is in beta.
       =20
        2) Replacing the non-open-source OROMatcher (which, frankly, I =

        =20
        3) Replacing the rather byzantine byaccj process with a grammar =

        =20
        4) Bytecode-compiling E rather than interpreting. Apart from =

        =20
        5) While we're compiling E, let's add support for multiple =

        =20
        Any thoughts on all of this?
        =20
        Paul
            -----Original Message-----
            From: Marc Stiegler <marcs@skyhunter.com>
            To: Paul Snively <psnively@earthlink.net>; =
e-lang@eros-os.org <e-lang@eros-os.org>
            Date: Monday, August 30, 1999 10:15 AM
            Subject: Re: Build Problems Resolved
           =20
           =20
            E seems to be a very, very intensive exerciser for jvms and =

            =20
            --marcs
            =20
                -----Original Message-----
                From: Paul Snively <psnively@earthlink.net>
                To: e-lang@eros-os.org <e-lang@eros-os.org>
                Date: Sunday, August 29, 1999 10:26 PM
                Subject: Build Problems Resolved
               =20
               =20
                Gentlemen,
                =20
                My apologies--I had suspected that I had to be =
overlooking something obvious, as I was.
                =20
                First of all, Mark, I did notice that it was necessary =

                =20
                The bigger issue, though, is that the Makefiles all have =

                =20
                Incidentally, I don't know why, but E 0.8.4 also breaks =

                =20
                Thanks for the help!
                Paul Snively
                <mailto:psnively@earthlink.net>
                =20

------=_NextPart_000_001F_01BEF394.07CAE780 Content-Type: text/html;

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">