A variant on the second option would be first defining
peg-string-compile to just throw an error, then redefining it later to
actually compile the string. That seems a little less hackish, at
least to me.
A fifth option would be to make peg-sexp-compile take an optional
argument FUN-RECUR that it
On Fri, Jan 28, 2011 at 9:07 PM, Noah Lavine wrote:
> Hello,
>
>> Indeed! I'm looking forward to having it in Guile.
>
> Great! I don't intend to be pressuring you to merge it, by the way. I
> hope my message didn't come across that way.
>
>> The reason I didn't merge it yet was twofold: (1) the
Putting it in single quotes should work. E.g. " '[' ". Similarly,
you can add a literal single quote by making it part of a character
class. E.g. " ['] ".
You're right, I should definitely add something about that to the documentation.
Any other weak parts you've noticed while perusing?
On Th
On Wed, Jan 26, 2011 at 8:38 PM, Noah Lavine wrote:
> Hello,
>
>> I'm the guy that originally wrote this for GSOC, so I figured I'd jump
>> in. I'd be happy to help with getting the PEG module merge-ready.
>
> Great!
>
>> keyword-flatten is described in api-peg.texi. It's basically a
>> special
Hi,
I'm the guy that originally wrote this for GSOC, so I figured I'd jump
in. I'd be happy to help with getting the PEG module merge-ready.
On Wed, Jan 26, 2011 at 7:40 PM, Noah Lavine wrote:
> Hello again,
>
> I've attached my coverage results. The html file expects the css file
> to be in th
On Fri, Aug 6, 2010 at 1:40 AM, Michael Lucy wrote:
> On Wed, Jul 28, 2010 at 12:13 AM, Michael Lucy wrote:
>> I've officially eliminated the last define-macro expression.
>>
>> However, I get the feeling that things may not be exactly as desired.
>> The origin
On Wed, Jul 28, 2010 at 12:13 AM, Michael Lucy wrote:
> I've officially eliminated the last define-macro expression.
>
> However, I get the feeling that things may not be exactly as desired.
> The original program made extensive use of functions in building the
> macros, and I
On Wed, Jul 28, 2010 at 12:41 AM, No Itisnt wrote:
> On Wed, Jul 28, 2010 at 12:13 AM, Michael Lucy wrote:
>
>> Another question about module namespaces: I have some syntax that I'd
>> like to be available to code generated by macros in my module, but
>> which I&#x
I've officially eliminated the last define-macro expression.
However, I get the feeling that things may not be exactly as desired.
The original program made extensive use of functions in building the
macros, and I originally tried to replace these with macros. This
turned out to be a little diffi
I'm still working on this. I haven't dropped off the face of the
earth; it's just taking a bit. The way I wrote the original
define-macro macros, they called some functions (passing in symbol
names) to generate blocks of code. This technique essentially depends
on variable capture, so I can't re
On Thu, Jul 8, 2010 at 11:21 AM, Andy Wingo wrote:
> Hi Michael,
>
> On Tue 06 Jul 2010 00:59, Michael Lucy writes:
>
>> (use-modules (ice-9 peg))
>> (peg-find "'b'+" "aabbcc")
>> --> (2 4 "bb")
>
> Humm, another thi
On Fri, Jul 9, 2010 at 2:58 AM, Michael Lucy wrote:
> On Thu, Jul 8, 2010 at 5:29 AM, Andy Wingo wrote:
>> A .texi file will be good, alongside the LALR(1) parser.
>
> Working on this now; should be done soon.
>
Pushed a first version of api-peg.texi up to origin/mluc
On Thu, Jul 8, 2010 at 5:29 AM, Andy Wingo wrote:
> Hi Michael,
>
> I am travelling currently, so a bit of asynchronicity in the reply :)
>
> On Mon 05 Jul 2010 07:05, Michael Lucy writes:
>
>> I finally got things into a usable state, so I pushed out what I have
>&
What form should I be writing external documentation in? The guile
manual on the website is in fairly straightforward html; should I be
writing in that?
On Mon, Jul 5, 2010 at 5:40 PM, Ludovic Courtès wrote:
> Hi!
>
> Thanks for the status report!
>
> Michael Lucy writes:
>
>> Files I've added so far:
>> guile/modules/ice-9/peg.scm (I assume this is the right place to put this?)
>
> No, it should rathe
Hi,
I finally got things into a usable state, so I pushed out what I have
to origin/mlucy. Many apologies if I did something wrong; I've never
used git with remote repositories before.
Files I've added so far:
guile/modules/ice-9/peg.scm (I assume this is the right place to put this?)
guile/test
On Thu, Jun 24, 2010 at 1:55 AM, Ken Raeburn wrote:
> On Jun 23, 2010, at 17:09, Michael Lucy wrote:
>> Is there any scheme expression that will just get ignored when the
>> scheme code is compiled?
>>
>> I'm generating some code with a function like:
>>
>
ot;*unspecified*") ;; *unspecified*
27(link-now)
28(variable-ref)
29(return)
scheme@(guile-user)>
If it's idiomatic I'll do that till I find something else though. Thanks!
On Wed, Jun 23, 2010 at 6:14 PM, No Itisnt wrote:
> On Wed, Jun 23, 2010 at 4:09 P
Hey,
Is there any scheme expression that will just get ignored when the
scheme code is compiled?
I'm generating some code with a function like:
(define (gen-update-ab updatea updateb)
`(begin
,(if updatea `(set! a (+ a 1)) `(donothing))
,(if updateb `(set! b (+ b 1)) `(donothing
Hey,
I'm generating some code, and I was wondering if:
((lambda (x) (* x 2)) 3)
is significantly less efficient than:
(* 3 2)
or if the Guile compiler will take care of that for me (the expression
is going to be evaluated a lot).
Hi,
I'm another of the GSOC students--I figured I'd introduce myself since
I may be asking questions on this list. I'm going to be writing a PEG
parser/matcher for Guile. My paperwork is still working its way
through the system so I can't point to any repositories where my code
will be yet, but
Hi,
On Mon, Mar 29, 2010 at 3:40 AM, Andy Wingo wrote:
>
> Tree-IL is the right thing IMO, mostly because it allows you keep source
> location information, but it also allows you to express more precisely
> what you want to compile to. You don't want to run your compiler's
> output through the Sc
On Fri, Mar 26, 2010 at 5:56 AM, Andy Wingo wrote:
> http://www.gnu.org/software/guile/mail/mail.html :) Guile-devel. Send
> things there, and copy me on them if you really want it to go to my
> attention.
Ah, OK, I thought you meant the summer-of-c...@gnu.org mailing list.
> Well, I've already
23 matches
Mail list logo
