unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: summer of code ideas
Date: Mon, 7 Mar 2011 12:23:31 -0800 (PST)	[thread overview]
Message-ID: <548800.13980.qm@web37904.mail.mud.yahoo.com> (raw)


>Hey all,
>
>We need to get together a few Guile-proposed projects for SoC students
>to hack on.  How about we collect them here in this thread.  I'll kick
>it off with one idea:
>
>  * A CPAN for Guile. 

A similar idea.

Define a syntax for use-modules to pull modules off the net, something 
like

   (use-modules (url://a-url.com library module #:optional a-rev-number))

Update modules on startup.  Cache modules and use last cached version if
internet access is not available.  Create server solution for modules.
Use openID or related to control access to Guile module server.  Use
revision-control-like system to server up proper revision of module.

Also, add syntax for procedure that, when called on local system,
actually execute on remote system.

(use-modules ((url://a-url.com library module #:optional a-rev-number)
              #:rpc external-func)) 

-Mike



             reply	other threads:[~2011-03-07 20:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 20:23 Mike Gran [this message]
2011-03-07 21:25 ` summer of code ideas Jose A. Ortega Ruiz
2011-03-08  1:10   ` Mark H Weaver
  -- strict thread matches above, loose matches on Subject: below --
2011-03-08  1:45 Mike Gran
2011-03-07 19:51 Andy Wingo
2011-03-07 20:12 ` Noah Lavine
2011-03-07 21:33   ` Ludovic Courtès
2011-03-07 22:11     ` Noah Lavine
2011-03-07 22:27       ` Ludovic Courtès
2011-03-07 22:37         ` Noah Lavine
2011-03-08 13:00           ` Ludovic Courtès
2011-03-07 20:40 ` Noah Lavine
2011-03-07 20:46   ` Andy Wingo
2011-03-07 21:27     ` Ludovic Courtès

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=548800.13980.qm@web37904.mail.mud.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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 read-only IMAP folder(s) and NNTP newsgroup(s).