9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Pegasus 2.6 is released
Date: Sun,  1 Feb 2009 12:12:05 +0100	[thread overview]
Message-ID: <8ccc8ba40902010312o25a52d57pd6a465f572e8079e@mail.gmail.com> (raw)
In-Reply-To: <4f34febc0901312327h2fe297bk490d3ee36faac5e@mail.gmail.com>

Can't you just execute new processes to "load" your
extensions?

I understand that's not a dll, but I'm really scared of
dlls after looking at what happen to linux. At least separate
binaries still work if you change libraries.

Just wondering.

On Sun, Feb 1, 2009 at 8:27 AM, John Barham <jbarham@gmail.com> wrote:
>> the argument that if the normal extension
>> mechanism for scripting languages is x,
>> thereforenot having x is a weakness seems
>> a version of argumentum ad populum.
>>
>> doesn't dynamic loading seem at odds with the
>> tools approach?  the more complex the interface,
>> the less general the tool.
>
> Dynamic loading allows scripting languages to load arbitrary binary
> extensions at run-time.  Without dynamic loading in Plan 9 you need to
> recompile the Lua (or Python) interpreters to statically link in your
> binary extensions, so in this case dynamic loading makes the tool more
> general.  (FWIW, as has been pointed out on this list previously,
> Inferno applications can dynamically load modules at run-time.)
>
>  John
>
>



  reply	other threads:[~2009-02-01 11:12 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01  4:29 Kenji Arisawa
2009-02-01  4:41 ` lucio
2009-02-01  4:47   ` Kenji Arisawa
2009-02-01  4:43 ` John Barham
2009-02-01  4:50   ` andrey mirtchovski
2009-02-01  5:47 ` John Barham
2009-02-01  6:44   ` erik quanstrom
2009-02-01  7:27     ` John Barham
2009-02-01 11:12       ` Francisco J Ballesteros [this message]
2009-02-01 12:56       ` erik quanstrom
2009-02-02 19:25       ` sqweek
2009-02-02 19:44         ` erik quanstrom
2009-02-02 19:49         ` Roman V. Shaposhnik
2009-02-02 21:22         ` John Barham
2009-02-02 21:27           ` erik quanstrom
2009-02-02 21:32           ` David Leimbach
2009-02-02 22:11             ` Roman V. Shaposhnik
2009-02-02 22:17               ` erik quanstrom
2009-02-02 22:30                 ` Anthony Sorace
2009-02-02 22:44                   ` erik quanstrom
2009-02-02 22:57                     ` Anthony Sorace
2009-02-02 23:04                       ` Bruce Ellis
2009-02-03  4:26                     ` lucio
2009-02-03  4:43                       ` Bruce Ellis
2009-02-03  6:38                       ` ron minnich
2009-02-02 23:18                   ` David Leimbach
2009-02-02 22:12             ` ron minnich
2009-02-02 22:14               ` erik quanstrom
2009-02-02 22:32                 ` ron minnich
2009-02-02 22:34                   ` erik quanstrom
2009-02-02 22:18               ` Roman V. Shaposhnik
2009-02-02 22:22                 ` Francisco J Ballesteros
2009-02-02 22:30                   ` Roman V. Shaposhnik
2009-02-03 10:55               ` Richard Miller
2009-02-03 16:03                 ` ron minnich
2009-02-03 16:07                   ` erik quanstrom
2009-02-03 16:48                     ` ron minnich
2009-02-03 17:01                       ` erik quanstrom
2009-02-02 22:07           ` Roman V. Shaposhnik
2009-02-01  7:31   ` [9fans] Dynamic loading et al (Was: Pegasus 2.6 is released) lucio
2009-02-01 17:26     ` ron minnich
2009-02-01 18:42       ` lucio
2009-02-01 20:14         ` ron minnich
2009-02-01 18:04     ` Dave Eckhardt
2009-02-01 18:39       ` lucio
2009-02-01 11:26   ` [9fans] Pegasus 2.6 is released Charles Forsyth
2009-02-01 11:56     ` lucio
2009-02-01 13:02       ` erik quanstrom
2009-02-02 17:38     ` John Barham
2009-02-02 17:48       ` ron minnich
2009-02-01  4:50 Kenji Arisawa

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=8ccc8ba40902010312o25a52d57pd6a465f572e8079e@mail.gmail.com \
    --to=nemo@lsub.org \
    --cc=9fans@9fans.net \
    /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).