9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] python
Date: Thu,  4 Jan 2007 23:26:34 -0800	[thread overview]
Message-ID: <cacc637eadad6e94a3eda0cf1a09f4d9@9netics.com> (raw)
In-Reply-To: <459DF84B.3010405@anvil.com>

how would this help with ldopen/LoadLibrary stuff?

while we're throwing out ideas, how about using filesystems to
implement the indirection that shared libs provide.  for a 'subsys'
instead loading a shared lib so we can write subsys.func1(params),
etc, provide an fs with hierarchy like:

	/subsys
		/func1
		/func2
		/func3

that implements the calls; then calls to subsys.func1(params,...)
would translate roughly to open/write(params)/read(result)/close of
the corresponding file.

> There may be the germ of an insane but possibly usable idea here ...
>
> What we need is a facility by which a program can glue together a bunch
> of object files
> when it's run ...
>> my slightly more thoughtful reaction is, why does the operating system need to control
>> the late-linking process?  (python doesn't really need .so shared libraries per se, does it?)
>> to me this seems more like a linker problem than anything else.  why not write your own?
>> you could write an rc script to gather the bits and waah laa. ... ooh, ron.  i just invented
>> linker scripts. ;-)
>>



  parent reply	other threads:[~2007-01-05  7:26 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 22:31 ron minnich
2007-01-05  4:14 ` John Barham
2007-01-05  6:18   ` erik quanstrom
2007-01-05  7:03     ` Dave Lukes
2007-01-05  7:09       ` Bruce Ellis
2007-01-05  7:26       ` Skip Tavakkolian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-10 14:06 [9fans] Python Michaelian Ennis
2010-10-10 14:21 ` Federico G. Benavento
2010-10-11  1:30   ` Michaelian Ennis
2010-10-11  1:55     ` Steve Simon
2010-10-11 23:59       ` Michaelian Ennis
2006-12-23 21:50 [9fans] python Bad-Santa
2006-12-23 23:54 ` ron minnich
2006-12-24  1:00   ` Russ Cox
2006-12-25  0:28     ` LiteStar numnums
2006-12-30  5:06       ` John Floren
2006-12-23  5:10 ron minnich
2006-12-23  5:27 ` Russ Cox
2006-12-23  5:31   ` ron minnich
2006-12-23  6:19     ` Russ Cox
2006-12-23  7:13       ` arisawa
2006-12-23 13:29   ` LiteStar numnums
2006-12-23 14:23     ` arisawa
2006-12-23 20:20       ` Russ Cox
2006-12-23 11:57 ` Matt
2003-11-03 16:11 matt
2003-11-03 15:20 ` Russ Cox
2002-03-11 18:51 Russ Cox
2002-03-18 13:21 ` Boyd Roberts
2002-02-08 13:51 Boyd Roberts
2001-12-06  7:29 Russ Cox
2001-12-06  7:17 ` Lucio De Re
2001-12-02  9:39 Russ Cox
2001-12-02 12:08 ` Boyd Roberts
     [not found] ` <rsc@plan9.bell-labs.com>
2001-12-02 16:05   ` Jonathan Sergent
2001-12-03 22:24 ` Laura Creighton
2000-11-06  8:26 [9fans] Python Jonathan Sergent
1999-01-16  5:53 arisawa
1998-12-30  0:17 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=cacc637eadad6e94a3eda0cf1a09f4d9@9netics.com \
    --to=9nut@9netics.com \
    --cc=9fans@cse.psu.edu \
    /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).