9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: ebo@sandien.com, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Binary format
Date: Wed, 17 Feb 2010 15:22:34 -0800	[thread overview]
Message-ID: <3e1162e61002171522tb34e196pf393f996d76a61ac@mail.gmail.com> (raw)
In-Reply-To: <twig.1266448563.32412@swcp.com>

[-- Attachment #1: Type: text/plain, Size: 2842 bytes --]

On Wed, Feb 17, 2010 at 3:16 PM, EBo <ebo@sandien.com> wrote:

> Nathaniel W Filardo <nwf@cs.jhu.edu> said:
>
> > On Wed, Feb 17, 2010 at 03:06:57PM +0100, Gorka Guardiola wrote:
> > > > * each module may have an entry point (main module w/o is allowed,
> > > >  even if it wouldn't make much sense ;-o), these are called after
> > > >  relocation, along the dependency tree, from leaf to root.
> > >
> > > no modules.
> >
> > That's not entirely true; there's (experimental ?) work for dynld(2), and
> > the shipping compilers can already produce DLMs.  (That said, libdynld is
> > not yet part of the base system.)  dynld(2) provides a system reminiscent
> of
> > dlopen() and dlsym(), but no dynamic linkage is supported (only dynamic
> > loading).  It is quite tastefully done and is useful to have for some
> > applications (the python port springs to mind).
>
> Is dynamic loading and linkage something that people want?  I have some old
> experimental code written in Spirit++ (a C++ template library which
> functionally replaces lex and yacc, and reads like EBNF).  The old code is
> for
> a runtime polymorphic parser for RS274 (CNC g-code).  I was experimenting
> with
> parsing historic CNC code, and play with different geometry engines.  This
> old
> project is WAY down on my to-get-around-to list, but it might be an
> interesting testbed for something later on.  This would be useful for stuff
> like a motion controller for the RepRap and DIY 3D Fab machines.
>
> For that matter, is there anything like Spirit++ <http://boost-spirit.com>
> in
> Plan9/Limbo?  When I developed the code for my fist thesis I developed a
> parser for some oddball finite difference equations produced by some
> modeling
> software.  It was nice to have the code read like EBNF.
>
>
Spirit is pretty amazing in that you can write very succinct and powerful
code with it, and yet it is terrible in that when you get an error message
you can end up with quite a disaster (due to the templates).  I particularly
like the Phoenix submodule in the new boost libraries for writing little
functional tidbits with STL looping constructs and iterators.

Speaking of which, Spirit appears to borrow pretty heavily from Parsec which
is a monadic parser combinator framework for Haskell that I believe will
work with Hugs, that also works on Plan 9.  (I think Andrey ported Hugs a
long time ago).

I'd LOVE to have GHC on Plan 9, but my first attempts to get anything
building with it were pretty frustrating.

There's scheme language implementations available for plan 9, and I think
one could either find or come up with a parsing framework like spirit for
scheme that relied on continuations (more "native" to scheme than monads,
though you could use monads too).

Dave


>  EBo --
>
>
>

[-- Attachment #2: Type: text/html, Size: 3606 bytes --]

  reply	other threads:[~2010-02-17 23:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 13:31 Enrico Weigelt
2010-02-17  8:50 ` Jacob Todd
2010-02-17 13:58   ` Enrico Weigelt
2010-02-17 14:01     ` erik quanstrom
2010-02-17 14:06 ` Gorka Guardiola
2010-02-17 14:13   ` David Leimbach
2010-02-17 14:33   ` Enrico Weigelt
2010-02-17 14:55     ` Steve Simon
2010-02-17 15:04       ` Enrico Weigelt
2010-02-17 15:29         ` erik quanstrom
2010-02-17 15:48         ` blstuart
2010-02-17 17:54           ` lucio
2010-02-17 18:37         ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-17 19:00         ` Nick LaForge
2010-02-18 15:08         ` Patrick Kelly
2010-02-17 15:58       ` David Leimbach
2010-02-17 16:14       ` Stuart Morrow
2010-02-17 16:28         ` David Leimbach
2010-02-17 18:21           ` Enrico Weigelt
2010-02-17 18:34             ` David Leimbach
2010-02-17 19:02               ` Enrico Weigelt
2010-02-17 19:35                 ` Enrico Weigelt
2010-02-17 18:38             ` Corey Thomasson
2010-02-18 15:16             ` Patrick Kelly
2010-02-17 15:13     ` Robert Raschke
2010-02-17 21:32     ` Jacob Todd
2010-02-17 21:26   ` Nathaniel W Filardo
2010-02-17 23:16     ` EBo
2010-02-17 23:22       ` David Leimbach [this message]
2010-02-17 14:38 ` blstuart
2010-02-17 14:58   ` Enrico Weigelt
2010-02-17 15:25     ` blstuart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e1162e61002171522tb34e196pf393f996d76a61ac@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@9fans.net \
    --cc=ebo@sandien.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).