unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: nalaginrut <nalaginrut@gmail.com>
To: Paul Raccuglia <praccugl@haverford.edu>
Cc: guile-devel@gnu.org
Subject: Re: Hi! Interested in GSoC. Feedback on these ideas?
Date: Thu, 07 Apr 2011 11:36:29 +0800	[thread overview]
Message-ID: <1302147389.2569.30.camel@Renee-desktop> (raw)
In-Reply-To: <BANLkTimxCQceZV=2mPpcuqwdTnwMi1tvaA@mail.gmail.com>

> Hi! I'm interested in working on guile as part of the Google Summer of Code.
> 
> I'm Paul Raccuglia, a Math/CS student at Haverford College (and
> general freelance hacker). I'm pretty excited by Guile, I think it's a
> cool project. I do a lot of Python coding, and I love interpreted
> languages; Guile seems like a great way to combine the comfort of
> interpreted languages with the general badassery of C.
> 
>  I've been talking with a friend who contributes to this project, and
> we came up with some exciting ideas for working on Guile over the
> summer.
> 
> Currently I am thinking about:
> 
> - A package manager (in the vein of apt-get)
> I know this is one that's come up a bit. I was thinking of writing a
> small web interface to browse packages, an aptitude style command-line
> method for downloading, verifying the hashes, checking dependencies,
> and then install the package(s) and an uninstall function as well. I
> saw the proposal of working with dorodango; I might look at it, but
> from what I saw of the code base, I thought it would make sense to try
> to write a GUILE specific package-manager.
> 

I like this. And I like the idea about GUILE specific package-manager.
Maybe you can learn something interesting from Nix, here is an
introduction from Nix website:
"Nix is a purely functional package manager. This means that it treats
packages like values in purely functional programming languages such as
Haskell — they are built by functions that don’t have side-effects, and
they never change after they have been built."
http://nixos.org/nix/

> 
> - AOT Compiler: write an interface to GCC
> I think this would be really cool. A good plan would be to use GCC,
> because it's already pretty sophisticated and handles lots of
> architectures. I would start by writing a scheme interface to GCC, and
> then writing the compiler in scheme.
> 
> I noticed a relevant (but now dead) project to write a GCC scheme
> compiler : http://gna.org/projects/gsc  ; they started in '05 and died
> by '06, but I think it would help me think through the process to look
> at what other people did.
> 

Well~I like this too~Actually I'm interested in GUILE in the embedded
device.So I'm looking for a good solution which could support nice
efficient for GUILE to run on embedded device.
The VM&bytecode maybe a good solution. But I'd like to see a GUILE
compiler which compile some code to binary directly(if it's possible).
I've tried Gambit-C, it's great. Can we do something alike for GUILE?

-- 
GNU Powered it
GPL Protected it
GOD Blessed it

HFG - NalaGinrut

--hacker key--
v4sw7CUSMhw6ln6pr8OSFck4ma9u8MLSOFw3WDXGm7g/l8Li6e7t4TNGSb8AGORTDLMen6g6RASZOGCHPa28s1MIr4p-x hackerkey.com
---end key---




  reply	other threads:[~2011-04-07  3:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07  0:40 Hi! Interested in GSoC. Feedback on these ideas? Paul Raccuglia
2011-04-07  3:36 ` nalaginrut [this message]
2011-04-07  8:31 ` Mark H Weaver
2011-04-07 13:10   ` Noah Lavine
2011-04-07 14:12     ` nalaginrut
2011-04-07 14:25     ` Problem with GCC as a Scheme compiler: tail calls Mark H Weaver
2011-04-07 14:37       ` Noah Lavine
2011-04-11 22:31         ` Andy Wingo
2011-04-11 23:12           ` Noah Lavine
2011-04-07 10:43 ` Hi! Interested in GSoC. Feedback on these ideas? Andreas Rottmann
2011-04-07 13:21   ` Paul Raccuglia
2011-04-07 21:45     ` Paul Raccuglia
2011-04-08  0:01       ` Paul Raccuglia
2011-04-08  1:00       ` dsmich
2011-04-08  4:36 ` Paul Raccuglia

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=1302147389.2569.30.camel@Renee-desktop \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=praccugl@haverford.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 read-only IMAP folder(s) and NNTP newsgroup(s).