From freiksenet at gmail.com Fri Dec 4 15:15:56 2009 From: freiksenet at gmail.com (Mikhail Novikov) Date: Fri, 04 Dec 2009 17:15:56 +0200 Subject: [Cl-yacc-ebnf-devel] Update Message-ID: <4B1927AC.5080500@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody! It had quite a busy week, so I was not able to do anything to the project, now I finally found some time and did some updates. I've added ":or" command. It is mostly added for developer convenience as there is already a way to have "or" in cl-yacc, but I've added it so that all syntax is uniform. Last thing to add to make proper ebnf is "except". Cheers, Mikhail -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksZJ6wACgkQPHyh4sfuKrkenQCeKMgjnWIsl8X4I/0PlUeGK41k Q7MAn1fsW6ZSDDSforQGPpwfyXSpQU8s =JxGU -----END PGP SIGNATURE----- From gtalk000 at gmail.com Sun Dec 6 03:37:38 2009 From: gtalk000 at gmail.com (Plato Wu) Date: Sun, 06 Dec 2009 11:37:38 +0800 Subject: [Cl-yacc-ebnf-devel] Hello, Sir In-Reply-To: <4B13488A.1020100@gmail.com> (Mikhail Novikov's message of "Mon, 30 Nov 2009 06:22:34 +0200") References: <873a3wn2xt.fsf@gmail.com> <4B13488A.1020100@gmail.com> Message-ID: <87ein8ydq5.fsf@gmail.com> I have made my clone based on your commit: d2c4cb50 and push one commit to implement define-ebnf-parser and add a simple EBNF example. Please check it and give your any suggestion. http://gitorious.org/~standin000/cl-yacc-ebnf/standin000s-cl-yacc-ebnf However I have to modify make-repeat for it is NG for me, I also add make-plus. I also check your commits after I cloned, I'm confusing what I should do next for you and me have done some duplicated jobs. I look forward to your reply. Best wishes Plato Wu From freiksenet at gmail.com Mon Dec 7 08:23:31 2009 From: freiksenet at gmail.com (Mikhail Novikov) Date: Mon, 07 Dec 2009 10:23:31 +0200 Subject: [Cl-yacc-ebnf-devel] Merge Message-ID: <4B1CBB83.5030207@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello! I've merged branch by Plato Wu to the master and added some refactoring, so all make-operation functions use make-or. I will start making a parser for "normal" ebnf grammar this week. Best regards, Mikhail -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkscu4MACgkQPHyh4sfuKrn5DwCeMwncUW+9sJEdWo9sUSfXAiem 8UcAn3jHTSMJh7MUDmyr9+yeXUKz5vrj =WIVH -----END PGP SIGNATURE----- From gtalk000 at gmail.com Wed Dec 9 05:58:36 2009 From: gtalk000 at gmail.com (Plato Wu) Date: Wed, 09 Dec 2009 13:58:36 +0800 Subject: [Cl-yacc-ebnf-devel] Merge In-Reply-To: <4B1CBB83.5030207@gmail.com> (Mikhail Novikov's message of "Mon, 07 Dec 2009 10:23:31 +0200") References: <4B1CBB83.5030207@gmail.com> Message-ID: <87my1swuwj.fsf@gmail.com> Mikhail Novikov writes: > Hello! > > I've merged branch by Plato Wu to the master and added some refactoring, so all > make-operation functions use make-or. > > I will start making a parser for "normal" ebnf grammar this week. > > Best regards, Mikhail > > _______________________________________________ > Cl-yacc-ebnf-devel mailing list > Cl-yacc-ebnf-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/cl-yacc-ebnf-devel But which task could I take for this project? Does parse-from-file just mean a wrapper for reading input from file? Best regards, Plato Wu. From freiksenet at gmail.com Sun Dec 27 09:48:24 2009 From: freiksenet at gmail.com (Mikhail Novikov) Date: Sun, 27 Dec 2009 11:48:24 +0200 Subject: [Cl-yacc-ebnf-devel] Parser for parsers Message-ID: <4B372D68.8020404@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello! I hope you had nice and happy holidays :) As you all know, the ebnf part of the cl-yacc is fully implemented and working and now there is a need to make parser for normal style ebnf grammar. As there are many modifications of ebnf grammar (standard, CLHS, extended) I though that it would be nice to have an abstraction layer on top of cl-yacc that allows to define grammar types in easy way. Basically, user provides cl-yacc grammar for the grammar type (like ebnf) and then it gets a closure which outputs a parser each time it receives actual grammar in previously given style. I have done this part, but now the problem is that it is very hard to generalize grammar styles, so definition of new grammar types is as tedious as normal parser grammar definition. I wonder if anyone have good ideas on how to abstract this kind of thing efficiently. Cheers, Mikhail -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAks3LWgACgkQPHyh4sfuKrn7XACfYBl74pN0Kpvau3s5Wlkpt+vS 1rMAnjAEaQ4FV5rUyE8clJO/24/9YE6r =wmW0 -----END PGP SIGNATURE-----