Hi,
A brief note to say that I have merged the PEG parser written by Michael
Lucy for GSOC 2010 to master.
I just noticed that I did the rebase incorrectly: the commit
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=eee0877c3e6ade8f2fa243cfa696918451c67aff
should have carried
Hi,
I was about to ask the savannah folks / gnu admins if they could change
the configuration for guile's repo to allow non-fast-forward pushes
(obviously with the --force or + flag). This would let me fix the
authorship in the recent PEG merge to master. It would also make it
easier to update
Hi Rob,
On Sat 11 Feb 2012 04:39, Rob Browning r...@defaultvalue.org writes:
Neil Jerram n...@ossau.homelinux.net writes:
Rob Browning r...@defaultvalue.org writes:
So do I understand correctly that in order for this to work, we'll first
need an updated libgc in Debian unstable?
Yes.
Hi!
Mark, are you still interested in implementing this? It would be very
nice :)
On Thu 16 Feb 2012 22:22, l...@gnu.org (Ludovic Courtès) writes:
Mark H Weaver m...@netris.org skribis:
l...@gnu.org (Ludovic Courtès) writes:
Mark H Weaver m...@netris.org skribis:
Here's a preliminary
Hi,
On Thu 23 Feb 2012 04:36, Mark H Weaver m...@netris.org writes:
Andy Wingo wi...@pobox.com writes:
On Fri 17 Feb 2012 12:00, l...@gnu.org (Ludovic Courtès) writes:
Commit f9685f437312ea790981373ddc375b2a26ba9c4f changes
‘build-lexical-var’ like this:
(define-syntax-rule
Hi,
On Thu 23 Feb 2012 15:53, Nala Ginrut nalagin...@gmail.com writes:
There's no mime support in Guile module, so I modified the mime code of
my project Ragnarok and format a patch.
It's easy to use:
(use-modules (web mime))
(define mime (make mime))
(mime:guess mime 'pdf)
==
On Wed, 2013-01-16 at 11:46 +0100, Andy Wingo wrote:
Hi,
On Thu 23 Feb 2012 15:53, Nala Ginrut nalagin...@gmail.com writes:
There's no mime support in Guile module, so I modified the mime code of
my project Ragnarok and format a patch.
It's easy to use:
(use-modules (web mime))
Hi,
Andy Wingo wi...@pobox.com skribis:
I was about to ask the savannah folks / gnu admins if they could change
the configuration for guile's repo to allow non-fast-forward pushes
(obviously with the --force or + flag). This would let me fix the
authorship in the recent PEG merge to master.
Hi,
Andy Wingo wi...@pobox.com skribis:
On Thu 23 Feb 2012 04:36, Mark H Weaver m...@netris.org writes:
Andy Wingo wi...@pobox.com writes:
On Fri 17 Feb 2012 12:00, l...@gnu.org (Ludovic Courtès) writes:
Commit f9685f437312ea790981373ddc375b2a26ba9c4f changes
‘build-lexical-var’ like
On Tue 28 Feb 2012 11:19, Nala Ginrut nalagin...@gmail.com writes:
I got extremely painful when I's tracing a complicated procedure. So I
decided to do something to alleviate this pain.
And I added a new print style for the REPL trace. It'll show level count
number instead lots of | |
On Wed 16 Jan 2013 13:17, l...@gnu.org (Ludovic Courtès) writes:
After re-reading the above, I think I’d prefer reintroducing white space
rather than using ‘$’.
Fine with me, it doesn't matter to me very much :) I just wondered if
you were still using the unused-lexical analysis, given that
hi Wingo!
Yes, it's a simpler solution for this, and less codes added.
But I still worried that folks may need to track the procedure call-stack
depth for debugging purpose. If we just limit '|||...' counting, it could
be implicit for the tracing, only ellipsis left...
What do you think?
On
On Wed 16 Jan 2013 13:55, Nala Ginrut nalagin...@gmail.com writes:
Yes, it's a simpler solution for this, and less codes added.
But I still worried that folks may need to track the procedure
call-stack depth for debugging purpose.
The patch does print out the number when it abbreviates;
Andy Wingo wi...@pobox.com skribis:
On Wed 16 Jan 2013 13:17, l...@gnu.org (Ludovic Courtès) writes:
After re-reading the above, I think I’d prefer reintroducing white space
rather than using ‘$’.
Fine with me, it doesn't matter to me very much :) I just wondered if
you were still using
If I set #:width 0, it'll print like the old patch, right?
It's nice if there's way to print all as depths, I think it's fine now. ;-)
On Wed, Jan 16, 2013 at 9:19 PM, Andy Wingo wi...@pobox.com wrote:
On Wed 16 Jan 2013 13:55, Nala Ginrut nalagin...@gmail.com writes:
Yes, it's a simpler
Hi,
Based on the consensus that we keep repeating, I finally changed our
manual to remove the generated standard library section and fold it
back into the Guile Modules documentation. However the docs are still
as bad as they ever were, and could use some overall reorganization as
well.
Is
Hi!
Andy Wingo wi...@pobox.com skribis:
But no, currently the answer is locale-specific. It encodes the string
according to the current locale, then decodes it from that encoding. If
your locale can't encode the string, tough luck for you!
SRFI-6 uses Unicode-capable ports since
Andy Wingo wi...@pobox.com skribis:
fix string-bytevector for utf-8 and non-error conversion strategies
* module/ice-9/iconv.scm (call-with-encoded-output-string):
(string-bytevector, bytevector-string): Only call string-utf8 and
utf8-string if the conversion
On Wed 16 Jan 2013 16:54, l...@gnu.org (Ludovic Courtès) writes:
As for bytevector-string, you should compare against
(%default-port-conversion-strategy) rather than 'error, I think.
Why do you say that? utf-8-string should always raise an error if it
detects invalid UTF-8, no?
Andy
--
Hi :)
On Wed 16 Jan 2013 16:44, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com skribis:
But no, currently the answer is locale-specific. It encodes the string
according to the current locale, then decodes it from that encoding. If
your locale can't encode the string,
On Wed 16 Jan 2013 15:46, Nala Ginrut nalagin...@gmail.com writes:
If I set #:width 0, it'll print like the old patch, right?
It's nice if there's way to print all as depths, I think it's fine now.
;-)
You would specify #:max-indent 0 -- #:width is for limiting total width.
,trace (test
Andy Wingo wi...@pobox.com skribis:
On Wed 16 Jan 2013 16:54, l...@gnu.org (Ludovic Courtès) writes:
As for bytevector-string, you should compare against
(%default-port-conversion-strategy) rather than 'error, I think.
Why do you say that? utf-8-string should always raise an error if it
On Tue 06 Mar 2012 10:55, Mark H Weaver m...@netris.org writes:
Here's an improved version of the Efficient Gensym Hack (v2).
Ping :) IIRC I had three substantive comments: that accessing the car
of a weak pair outside the alloc lock is not a good idea; that
allocating within a mutex can
Andy Wingo wi...@pobox.com skribis:
Otherwise, %default-port-encoding governs (info (guile) String Ports):
But why?
Because %default-port-encoding specifies the default port encoding? :-)
I think that was mostly the reason behind
http://thread.gmane.org/gmane.lisp.guile.devel/9822.
You
On Wed 07 Mar 2012 17:32, Nala Ginrut nalagin...@gmail.com writes:
(call-with-input-string asdf (lambda (port) (read-delimited @ port
'fail
LGTM; just missing a test case. I would tighten up the documentation,
too: make sure each sentence is actually a sentence. (It's a common
mistake,
Hi Noah,
A question from a while back, but hey, an answer:
On Wed 14 Mar 2012 01:43, Noah Lavine noah.b.lav...@gmail.com writes:
It's not intuitive that a function that is available by at the REPL is
not available in a module. [referring to `compile']
There are a few more things that are
On Wed 16 Jan 2013 18:37, l...@gnu.org (Ludovic Courtès) writes:
I just think this may have to wait until 2.2.
WDYT?
Oh yes, agreed here. Anyway let's let it simmer for a while. Another
two or three of these threads should be enough to either reaffirm or
change the current state of things
Hi,
On Sun 18 Mar 2012 16:05, Stefan Israelsson Tampe stefan.ita...@gmail.com
writes:
It is possible to get syntax location information via syntax-source, but
trying to implement
something like
(define-syntax syntax/loc
(syntax-rules ()
((_ src stx)
(let ((ret (syntax stx)))
28 matches
Mail list logo
