[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hello World

From: Noah Lavine
Subject: Re: Hello World
Date: Mon, 9 Apr 2012 21:37:26 -0400


Well, you started the right way by emailing guile-devel. If you're not
already, you should be subscribed to this mailing list. That way
you'll know what's going on in Guile. This is also where you can
discuss any ideas you have for it (if you don't have them now, you
will soon).

First of all, if you have a project you want to do, do it. If you want
to improve Guile, that's great, and if you want to make an application
using Guile, you can discover what features Guile is missing and help
us add them, which is also useful.

But it sounds like you don't know what you want to do. In that case, I
have an idea for you: make a parser for C. The long-term goal would be
to make Guile automatically connect to C libraries by parsing their
header files, but a C parser is the first step. Guile has a built-in
library for parsing yacc/bison-style grammars, and another library for
parsing PEG grammars that has almost been merged but is waiting in a
branch. You could pick whichever one you want and start with that.

I think you'll find that the hardest part is dealing with the
preprocessor. I think the best thing is to only parse C files where
preprocessor #define's are also C expressions or statements, and any
#ifdef's have the same grammatical form in both alternatives. That
should get everything except very obfuscated C, which is fine for this

Is that a project you're interested in? If not, it's fine - there are
plenty of other things to do. It is important that you have a project
that you like.


2012/4/5 Cameron Che <address@hidden>:
> Hi Noah,
> Thanks for the helpful information you have given. That's very appreciated.
> I know a bit Scheme although I have been working on common and elisp more.
> I am interested in quite a few things like C, operating systems, file
> system, the web stuff,
> Java etc. And I really like get to know the core of guile. However I think
> it would be
> hard for me to start looking at the kernel stuff just for now.
> It would be easier to start from outside towards inside, right?.
> Could you give any suggestions upon which part? And is there any part that
> need to be improved or patched? If there is I am more than happy to do some,
> hopefully.
> Thanks again for all the help.
> Cameron
> 在 2012年4月3日 下午9:15,Noah Lavine <address@hidden>写道:
>> Hello,
>> Thanks for emailing! Yes, you can definitely get involved. We always
>> like having new people appear and help.
>> Here is how it works, more or less: you'll work on some part of Guile
>> - you get to pick this. When you have an improvement, you'll email it
>> to the list as a series of patches. The patches will be reviewed, and
>> people might suggest improvements. It's normal to write several
>> versions of a patch before it's used, so don't feel worried about
>> that. When your patches are ready, someone will commit them to
>> mainline Guile, and then you will have contributed!
>> If you already know Scheme, then the main thing you will need to do is
>> learn git, which is the revision control system we use. There are lots
>> of tutorials on the internet.
>> The other thing you will need is some part of Guile you want to work
>> on. Do you know what sort of things you are interested in?
>> Thanks for emailing,
>> Noah
>> On Sat, Mar 31, 2012 at 10:38 PM, Cameron Che <address@hidden> wrote:
>> > Hi Guys,
>> >
>> > This is Cameron. I have Just joined this mailing list. Have been
>> > interesting
>> > in Lisp for years.
>> > And did a quite few hacking of it.
>> > I'd like to say hi. and ask a question.
>> >
>> > Since, I really like to get involved in all the developing stuff.
>> > I would like to know how does all you guys function?
>> > And is there any needs for new guys like me to do some codings?
>> >
>> > Any help is appreciated.
>> > Cheers
>> >
>> > Cameron Che
>> >
>> >
>> >
>> >
>> >
>> >
>> >

reply via email to

[Prev in Thread] Current Thread [Next in Thread]