Re: imagining a programming language with a capability calling convention
Mark Miller <[email protected]> Mon, 14 Sep 2015 09:01:34 -0400
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <CAK5yZYhsYdbwp87okk=gyuQ=4n=Ga8rYfcx7zGMMhU3ai8bvpw@mail.gmail.com> |
On Sun, Sep 13, 2015 at 11:48 PM, Raoul Duke <[email protected]> wrote: > > If we're talking about memory safe languages, why lame? > > paranoid hedging of bet. e.g. watch out for reflection? > > > If creation does not violate the connectivity laws nor cause external > > effects, what's the problem? > > uh, are those the case in bog-standard run-of-the-mill languages & > environments? > > i mean since there are projects to e.g. tame Java, Ocaml, JavaScript, > you name it, there are probably plenty of problems with our "standard > OOP" languages. None of the problems with those languages are with their mechanisms for calling or creation. As an ocap call mechanism, their calling mechanisms are all fine. -- Cheers, --MarkM _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk