unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: Issues in ia64
Date: Tue, 02 Jul 2002 15:35:56 -0700	[thread overview]
Message-ID: <E17PWFY-0007eq-00@giblet> (raw)
In-Reply-To: <F190nR65CbkvKC4iDir00003774@hotmail.com> (cr88192@hotmail.com)

   From: "cr88192 sydney" <cr88192@hotmail.com>
   Date: Tue, 02 Jul 2002 21:18:08 +0000

   err?...

for example, getpwent binding (glue code) can be put into a shared
object library and then we can arrange for guile to load that library
automatically on first reference to `getpwent'.  all this is "can"
because no one has actually done it yet.  part of the problem is
settling on methodology to make this particular separation an instance
of the larger task of "supporting modular development".  everything can
be done by hand but that gets old...

   what I had done with it would was using it as a lib, but all the
   "normal" extensions loaded in (ice-9, guile-gtk, ...). didn't work
   and couldn't be loaded without putting them in the current
   directory...

did you load boot-9.scm?  this defines the module system, which is what
searches `%load-path' for those things.

   ok, the real issue is that I don't know guile's workings in detail...

i'm in the same boat (whatever level of detail i know, there's always a
deeper level).

   I have for a while been considering writting a compile system, I had
   written a general spec for the calling convention and how to handle
   precise gc/relocation/swizzling for the stack, if wanted I may be
   able to make the partial spec available. are there any real important
   issues for this?

important issues for compilation are everywhere.  important issues for
your spec are that it be complete, consistent and implementable.  less
clearly important (i.e., may be important to some people but not to you)
is that it interoperate w/ current designs, to aid experimentation.

   in my spec call/cc is accomplished by copying the pages from the
   stack region into a continuation region and setting the real stack
   copy-on-write, is this good?

i don't know enough about the particulars to answer this.

   question: in guile anyways is it possible to supply your own mm and
   to inquire about the structure of objects? is there a spec on the
   structure of objects as well?...

guile implements a mini language for specifying object layout in memory.
see libguile/struct.c `make-struct-layout'.  user-level docs are in the
manual under node `Structures':

 http://www.glug.org/docbits/guile-doc-out/html/guile-1.7.0/guile_25.html#SEC237        
                                               
i don't know what "your own memory management" means, precisely.
certainly guile abstracts malloc and free for its own use internally.

thi

_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2002-07-02 22:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02 21:18 Issues in ia64 cr88192 sydney
2002-07-02 22:35 ` Thien-Thi Nguyen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-03  0:58 cr88192 sydney
2002-07-02  2:53 cr88192 sydney
2002-07-02 10:04 ` Thien-Thi Nguyen
     [not found] <20020629160009.7829.18795.Mailman@fencepost.gnu.org>
2002-07-02  0:37 ` Ying Luo
2002-07-02  8:58   ` Thien-Thi Nguyen
2002-07-02  9:59     ` Thien-Thi Nguyen
2002-07-02 19:01     ` Marius Vollmer
2002-07-06  1:54       ` Thien-Thi Nguyen
2002-07-02 18:24   ` Marius Vollmer
2002-07-10  6:30     ` Rob Browning

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=E17PWFY-0007eq-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=guile-user@gnu.org \
    --cc=ttn@glug.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).