> bugfix bundle!
Awesome!! Merged and pushed.
In the future, I recommend that you add a testcase when you do a bugfix. In
fact, you should probably add the testcase & commit first (aka test-driven
development). That way, we can be more confident that it got fixed and will
*stay* fixed :-).
Yet another bundle!!
This adds spec-* to the distributed tarball.
Sincerely,
AmkG
2012-08-01-almkglor-2.bundle
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways to
bugfix bundle!
Sincerely,
AmkG
2012-08-01-almkglor.bundle
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and h
Alan Manuel Gloria:
> bundle me one more time!
All applied. I also changed the software version number to 0.3.0.
--- David A. Wheeler
--
Live Security Virtual Conference
Exclusive live event will cover all the ways toda
bundle me one more time!
fix up some mistakes in man files, allow command-line arguments on
sweeten and unsweeten
On Tue, Jul 31, 2012 at 4:52 AM, Alan Manuel Gloria wrote:
> bundle!
>
> finally remove my-unread-char
2012-07-31-almkglor-2.bundle
Description: Binary data
---
bundle!
finally remove my-unread-char
2012-07-31-almkglor.bundle
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has change
bundle time! Just minor tweaks.
2012-07-30-almkglor.bundle
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and
> > Alan Manuel Gloria:
> >> Handle multiline comments and other #-foolery.
> >>
> >> TODO: Need to add #{weird symbol}# syntax to Guile
> >> compatibility layer.
> >
> > Youch, that's a lot of complexity to implement what is notionally a simple
> > capability.
> >
> > I'm not su
On Sat, Jul 28, 2012 at 6:45 PM, David A. Wheeler wrote:
> Alan Manuel Gloria:
>> Handle multiline comments and other #-foolery.
>>
>> TODO: Need to add #{weird symbol}# syntax to Guile
>> compatibility layer.
>
> Youch, that's a lot of complexity to implement what is notionally
Alan Manuel Gloria
> yet another bundles the dust!!
AWESOME. Everyone: this bundle implements sublists. Nice job. It's such a
straightforward implementation that it looks "obviously right" (it might be
wrong, but it *looks* right to me). And I really appreciate the test cases,
too.
Pushed.
Alan Manuel Gloria:
> Handle multiline comments and other #-foolery.
>
> TODO: Need to add #{weird symbol}# syntax to Guile
> compatibility layer.
Youch, that's a lot of complexity to implement what is notionally a simple
capability.
I'm not sure I understand why this is so co
yet another bundles the dust!!
On Sat, Jul 28, 2012 at 6:02 PM, Alan Manuel Gloria wrote:
> You know that feeling when you receive a bundle on your inbox? No?
> THEN FEEEL IT NOWW!!
>
> commit 5fa425f68af901bc0de55dd89f541099d7365dd0
> Author: Alan Manuel K. Gloria
> Date: Sat Jul 28 17:5
You know that feeling when you receive a bundle on your inbox? No?
THEN FEEEL IT NOWW!!
commit 5fa425f68af901bc0de55dd89f541099d7365dd0
Author: Alan Manuel K. Gloria
Date: Sat Jul 28 17:58:14 2012 +0800
Handle multiline comments and other #-foolery.
TODO: Need to add #{weird sy
On Sat, Jul 28, 2012 at 5:49 AM, David A. Wheeler wrote:
> Alan Manuel Gloria:
>> buNDlE BunDEl
>
> Awesome, pushed.
>
> And we have a new kind of error: If you use "!" indents, and later
> split a line, this won't work:
> !hello( ...
> !
> !)
> Because the "!"
Alan Manuel Gloria:
> buNDlE BunDEl
Awesome, pushed.
And we have a new kind of error: If you use "!" indents, and later
split a line, this won't work:
!hello( ...
!
!)
Because the "!" on the middle and last line are *NOT* indent chars.
I'm really striving to m
buNDlE BunDEl
On Thu, Jul 26, 2012 at 5:59 AM, Alan Manuel Gloria wrote:
> bundle bundle
2012-07-28-almkglor.bundle
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the wa
bundle bundle
2012-07-26-almkglor.bundle
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can
I also checked, and #' #` #, #,@ are all R6RS-standard abbreviations,
for (syntax ..) (quasisyntax ...) (unsyntax ...) and
(unsyntax-splicing ...). Guile 2.0 defines those to be the same as in
R6RS.
However
On Guile 1.6 and 1.8, #' seems to be something completely different.
Here are stuff:
On Wed, Jul 25, 2012 at 8:26 AM, David A. Wheeler wrote:
> Alan Manuel Gloria:
>> So... no more unread-char? Do I remove the unread-char impl as well
>> as the 2nd char buffer on R5RS compatibility layer?
>
> Yes, please do. That would simplify things, and it was the reason we
> switched to "!"
> Nah, I *like* autotools, they let me compile stuff on systems that
> don't have autotools. It's the only build system I know that has that
> property.
Okay, I'm autoconfiscating.
--- David A. Wheeler
--
Live Security
Alan Manuel Gloria:
> So... no more unread-char? Do I remove the unread-char impl as well
> as the 2nd char buffer on R5RS compatibility layer?
Yes, please do. That would simplify things, and it was the reason we switched
to "!" as the non-whitespace indent character.
On a related note: I sta
So... no more unread-char? Do I remove the unread-char impl as well
as the 2nd char buffer on R5RS compatibility layer?
Sincerely,
AmkG
--
Live Security Virtual Conference
Exclusive live event will cover all the ways tod
On Tue, Jul 24, 2012 at 5:59 PM, David A. Wheeler wrote:
> (If you have an autotools allergy, let me know, but they're the obvious way
> to do this.)
Nah, I *like* autotools, they let me compile stuff on systems that
don't have autotools. It's the only build system I know that has that
property
Alan Manuel Gloria:
> In short: this is a lot of work for little gain (specifically, so that
> use-modules will work correctly on Guile 2.0 when autocompilation is
> turned OFF). We can just say that currently, on Guile 2.0,
> autocompilation (the default) needs to be enabled in order to work
> pr
On 7/24/12, Alan Manuel Gloria wrote:
> On 7/22/12, Alan Manuel Gloria wrote:
>> Ridiculously big bundle time!!
>>
>> It's the big reorg!!!
>>
>> There are some ridiculous issues with Guile 2.0 and auto
>> compilation in particular, autocompilation needs to be ON
>> otherwise replace-read wil
On 7/22/12, Alan Manuel Gloria wrote:
> Ridiculously big bundle time!!
>
> It's the big reorg!!!
>
> There are some ridiculous issues with Guile 2.0 and auto
> compilation in particular, autocompilation needs to be ON
> otherwise replace-read will only work on the REPL, not inside
> use-module
On 7/24/12, David A. Wheeler wrote:
> So I think this would be the (readable sweeten) module. The fact that it's
> written in sweet-expressions presents a fun bootstrapping issue :-).
(^^) Not at all. If you were to write (readable
color-of-the-bikeshed-issue) in sweet-expressions, *then* you g
I said:
> > How about naming "sweet-impl" to "kernel", so we can say:
> > readable kernel
Alan Manuel Gloria said:
> Okay, give me a name when you've decided. I've decided that all name
> issues are color of the bikeshed issues and will not object, as long
> as they're not some kind of obvious
On 7/24/12, David A. Wheeler wrote:
> Alan Manuel Gloria:
>> Is it bundle time again??
>> Yes it is!!
>
> Excellent!
>
> This makes me think we need to rename some things. In particular:
> readable sweet-impl
> seems weird. That module implements not just sweet, but all the notations.
>
> How a
Alan Manuel Gloria:
> Is it bundle time again??
> Yes it is!!
Excellent!
This makes me think we need to rename some things. In particular:
readable sweet-impl
seems weird. That module implements not just sweet, but all the notations.
How about naming "sweet-impl" to "kernel", so we can say:
Regarding Guile "-s" - This is required on Guile 1.6. On Guile 1.6 a
flat "guile sweeten.scm" will fail, with Guile complaining that it
does not recognize sweeten.scm as an option. On Guile 1.8 and 2.0 the
flag is ignored.
-
Is it bundle time again??
Yes it is!!
commit 5605bde7241b6601f4c16576ca96112f83b8cd39
Author: Alan Manuel K. Gloria
Date: Tue Jul 24 06:10:42 2012 +0800
Use restore-scheme-read() to restore the Scheme reader.
commit 61ff2441508c22f7d851e540bcca4ae9206e408b
Author: Alan Manuel K. Gloria
ridiculously tiny bundle time!
Just a modification of sweeten script to execute sweeten.sscm without
passing through the unsweetener.
Sincerely,
AmkG
2012-07-23-almkglor.bundle
Description: Binary data
--
Live Security
Alan Manuel Gloria said:
> Ridiculously big bundle time!!
>
> It's the big reorg!!!
Sure is! But I looked over the deltas, and the test cases all work too.
So I've already applied and pushed.
> There are some ridiculous issues with Guile 2.0 and auto
> compilation in particular, autocompila
Ridiculously big bundle time!!
It's the big reorg!!!
There are some ridiculous issues with Guile 2.0 and auto
compilation in particular, autocompilation needs to be ON
otherwise replace-read will only work on the REPL, not inside
use-modules... WEIRD.
Also, we need to properly suppor
Alan Manuel Gloria
> Okay, here's the public interface:
Overall that looks pretty nice. Comments below.
> define-module
> readable sweet-impl
> :export
> \\
> . ; tier readers
> . curly-infix-read ; :: Port -> Object
> . modern-read ; :: Port -> Object
> . sweet-read ; :: Port ->
On Sat, Jul 21, 2012 at 10:48 AM, David A. Wheeler
wrote:
> Alan Manuel Gloria:
>> Okay, so somehow everything is going to be prefixed with (readable
>> ...) and now everyone is arguing about the exact name. In the mean
>> time I'll just reorg the code, I hope the name gets settled by the
>> time
Alan Manuel Gloria:
> Okay, so somehow everything is going to be prefixed with (readable
> ...) and now everyone is arguing about the exact name. In the mean
> time I'll just reorg the code, I hope the name gets settled by the
> time I finish and I'll just do some sort of s/whatever/whatever/
Sou
Okay, so somehow everything is going to be prefixed with (readable
...) and now everyone is arguing about the exact name. In the mean
time I'll just reorg the code, I hope the name gets settled by the
time I finish and I'll just do some sort of s/whatever/whatever/
(^.^)v have fun!
-
>
> > > I dislike the name "modern-expressions"
>
> Can you propose some alternative names?
>
It was my understanding that "modern-expressions" was the name of the rule
that transformed the standard s-expr
(function arg1 arg2 arg3)
into the sweet-expression form
function(arg1 arg2 arg3)
It is
> One problem I see is that one-letter names (like "c-expressions" for curly
> infix, "m-expressions" for modern expressions, and "t-expressions" for sweet
> expressions) don't really have the same "punch".
>
> What names would you propose for all 4 cases, and why?
It might make sense to think a
> I like the word "modern" expressions because who wants to AVOID doing things
> the "modern" way? And wouldn't you want to use a "sweet" notation? Just
> letters don't do that.
Positive-association names are a double-edged thing. One the one hand
they create positive associations. On the othe
>> > texprs
>
> I don't like this as a name, it's not obvious how to pronounce it.
You know, I've never known how to pronounce s-expressions either..
ess expressions => tee expressions
sexpers => texpers
sexpees => texpees
Perhaps I like the name because of my time in texas :p
---
Alpheus Madsen:
> I have an odd suggestion for a naming convention for these things: call them
> "texprs", with submodules "curly-texprs", "whitespace-texprs", and
> "function-texprs". (I dislike the name "modern-expressions" because standard
> functional notation is rather old, which is what
> > I dislike the name "modern-expressions"
Can you propose some alternative names?
> > texprs
I don't like this as a name, it's not obvious how to pronounce it.
--- David A. Wheeler
--
Live Security Virtual Conference
>> "readable" seems generic. How about 'sweetexpr'?
>
> The problem is that sweet-expressions are only one of 3 tiers.
There's lots of precedent for a broad category to have the same name
as a sub-category. Like 'cat'. We don't have to be perfectly
consistent in choosing names, only in using them.
> texprs
I like it!
> I dislike the name "modern-expressions"
+1
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers ca
I have an odd suggestion for a naming convention for these things: call
them "texprs", with submodules "curly-texprs", "whitespace-texprs", and
"function-texprs". (I dislike the name "modern-expressions" because
standard functional notation is rather old, which is what makes it seem so
natural.)
Kartik Agaram:
>
> "readable" seems generic. How about 'sweetexpr'?
The problem is that sweet-expressions are only one of 3 tiers. Some people
will not adopt the whole tier, but if they can accept curly-infix, that's still
an improvement. I very much intend for people to be able to adopt any
Alan Manuel Gloria:
> Ah, I see. My main concern was that the current module structure has
> sugar separately loadable from modern, so I thought you wanted to
> retain that, but use a more Scheme-y interface. So if you prefer to
> have complete integration of modern into sugar, that's fine. You
Alan Manuel Gloria:
> Wait wait wait. Isn't the typical protocol to put the provenance of a
> module somewhere in it's hierarchical name?
Sure!
> Since sweet-expr are a
> project of the readable-discuss mailinglist, I thought it best to put
> the name readable-discuss on it. Basically, the mod
On Fri, Jul 20, 2012 at 8:40 PM, David A. Wheeler wrote:
> Alan Manuel Gloria:
>> I think I want to reorganize them module's interfaces.
>>
>> And I think I want to put them in a readable-discuss subdirectory so
>> that module names are something like (readable-discuss sugar) or some
>> such. Tha
On Fri, Jul 20, 2012 at 8:40 PM, David A. Wheeler wrote:
> I kept the "sugar" system separate because I thought we were just going to
> use SRFI-49 as-is, possibly with some bug fixes. Obviously that is NOT the
> case. While we *could* keep the "sweet" system separate and able to build on
> o
> We need to have *REALLY GOOD NAMES* for the public interface. Good names
> make all the difference for ease-of-use. For example, don't use the name
> "readable-discuss" - that's the mailing list name, not the group name, and
> it's long anyway. But "readable" as a module name might work. A
Alan Manuel Gloria:
> I think I want to reorganize them module's interfaces.
>
> And I think I want to put them in a readable-discuss subdirectory so
> that module names are something like (readable-discuss sugar) or some
> such. That will help making them easier to fob around in various
> Scheme
On 7/20/12, David A. Wheeler wrote:
> On Fri, 20 Jul 2012 00:37:57 +0800, from Alan Manuel Gloria:
>> bundle bundle!
>
> Awesome. Reviewed, accepted, pushed.
>
> More tests == more goodness, and I am *REALLY* glad to be rid of the ugly
> function clean(). I'm sure more code cleanups would help,
On Fri, 20 Jul 2012 00:37:57 +0800, from Alan Manuel Gloria:
> bundle bundle!
Awesome. Reviewed, accepted, pushed.
More tests == more goodness, and I am *REALLY* glad to be rid of the ugly
function clean(). I'm sure more code cleanups would help, but that's a big
step forward.
And speaking o
bundle bundle!
2012-07-20-almkglor.bundle
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers ca
On 7/19/12, David A. Wheeler wrote:
> Alan Manuel Gloria:
>> Heya, looked at commit c94afdb0b89b1c1e2b8ec26111aef68308d59bd2,
>
> Awesome, and thanks. I'm a big believer in peer review.
>
>
>> This seems different, shouldn't that be:
>>
>> +(if (or (char-whitespace? char) (eqv? #\newline char
Alan Manuel Gloria:
> Heya, looked at commit c94afdb0b89b1c1e2b8ec26111aef68308d59bd2,
Awesome, and thanks. I'm a big believer in peer review.
> This seems different, shouldn't that be:
>
> +(if (or (char-whitespace? char) (eqv? #\newline char))
> +(list qt)
> +(list qt (su
Heya, looked at commit c94afdb0b89b1c1e2b8ec26111aef68308d59bd2,
+; Return #t if char is space or tab.
+(define (char-horiz-whitespace? char)
+ (or (eqv? char #\space)
+ (eqv? char tab)))
+
(define sugar-read-save read)
(define (consume-to-eol port)
@@ -86,11 +94,9 @@
(define (readquote
On Thu, Jul 19, 2012 at 6:30 AM, David A. Wheeler wrote:
> Alan Manuel Gloria
>> Bundle time!
> ...
>> commit 4492dc4a42c5d6b3553491fe36a8b9c1d6bfbe1a
>> Author: Alan Manuel K. Gloria
>> Date: Thu Jul 19 06:20:03 2012 +0800
>>
>> Add example nfx macro implementation.
>>
>> This very
Alan Manuel Gloria
> Bundle time!
...
> commit 4492dc4a42c5d6b3553491fe36a8b9c1d6bfbe1a
> Author: Alan Manuel K. Gloria
> Date: Thu Jul 19 06:20:03 2012 +0800
>
> Add example nfx macro implementation.
>
> This very simple implementation of nfx allows
> very simple arithmetic
Bundle time!
Not much I'm afraid...
commit 4492dc4a42c5d6b3553491fe36a8b9c1d6bfbe1a
Author: Alan Manuel K. Gloria
Date: Thu Jul 19 06:20:03 2012 +0800
Add example nfx macro implementation.
This very simple implementation of nfx allows
very simple arithmetic precedence, and
Alan Manuel Gloria:
> This improves passing rate of sweet-test. Only one fails:
> '(x y)
> ' group
>x y
>
> You know, my personal interpretation is that this is: ...
> '((x y))
>
> So is the test wrong in this case?
The test case is absolutely wrong, and you are right.
I've pushed a fix.
Alan Manuel Gloria:
> bundle bundle bundle
Awesome, I looked over, look great and pushed them to the project repository.
> sugar.scm: Handle quote et al. better
>
> Do it in readblock, which matches the actual spec more.
> Also preparation for removal of clean() function, which
>
On Mon, Jul 16, 2012 at 9:40 PM, Alan Manuel Gloria wrote:
> bundle bundle bundle
>
> commit e595889b84d647c905052eb13b91973e67b10db1
> Author: Alan Manuel K. Gloria
> Date: Mon Jul 16 21:35:49 2012 +0800
>
> sugar.scm: Handle quote et al. better
>
> Do it in readblock, which matches
bundle bundle bundle
commit e595889b84d647c905052eb13b91973e67b10db1
Author: Alan Manuel K. Gloria
Date: Mon Jul 16 21:35:49 2012 +0800
sugar.scm: Handle quote et al. better
Do it in readblock, which matches the actual spec more.
Also preparation for removal of clean() functio
On Sun, Jul 15, 2012 at 7:11 PM, David A. Wheeler wrote:
>> Yet another bundle!
>
> Awesome. Accepted.
>
> I really am reviewing every commit. I really appreciate the nicely focused
> changes in each commit, you've made them quite easy to review.
>
>> commit a9c142b5377dd1537508556da31d9a21c2ac
> Yet another bundle!
Awesome. Accepted.
I really am reviewing every commit. I really appreciate the nicely focused
changes in each commit, you've made them quite easy to review.
> commit a9c142b5377dd1537508556da31d9a21c2ac02c4
> Author: Alan Manuel K. Gloria
> Date: Sun Jul 15 15:17:44 2
Yet another bundle!
commit a9c142b5377dd1537508556da31d9a21c2ac02c4
Author: Alan Manuel K. Gloria
Date: Sun Jul 15 15:17:44 2012 +0800
Added another example: list-of macro (list comprehension macro)
commit 3b4674eba67d64e2d5b66c5b1d2fb44c82031ffa
Author: Alan Manuel K. Gloria
Date: Sun
Alan Manuel Gloria:
> Currently fails!!
> (;comment
> )
>
> Results in:
>
> (#{}#)
>
> Expected result:
>
> ()
>
> Looks like a bug in modern.scm?
>
> Will dig, probably tomorrow. Need to sleep.
Okay. I added that to the testsuite.
--- David A. Wheeler
---
On Fri, Jul 13, 2012 at 7:45 AM, David A. Wheeler wrote:
> Alan Manuel Gloria:
>
>> fix done (attached bundle), I used a different tag variable instead of
>> re-using group.
>
> Awesome. Applied.
>
> I also added a test case to check for this, so we don't regress. Feel free
> to add more test ca
Alan Manuel Gloria:
> fix done (attached bundle), I used a different tag variable instead of
> re-using group.
Awesome. Applied.
I also added a test case to check for this, so we don't regress. Feel free to
add more test cases!
BTW, I plan to remove the "CHANGES" section - git can track that
fix done (attached bundle), I used a different tag variable instead of
re-using group.
Some code issues:
1. The group variable isn't used. At all. Looking at SRFI-49, it
looks like it is not used even in the reference implementation.
2. I think the existence of the clean function is an abomi
On Thu, Jul 12, 2012 at 6:21 AM, David A. Wheeler wrote:
>> New bundle time!
>
> Awesome!
>
>> First bundle: 2012-07-11-almkglor-comment-only.bundle - just
>> additional comments, plus a no-op change in modern.scm (a bugfix in a
>> part of the code that never gets called anyway)
>
> All in.
>
>> S
On Wed, Jul 11, 2012 at 9:34 AM, David A. Wheeler wrote:
> Alan Manuel Gloria
>> Have a new bundle - this is dependent on the earlier bundle.
>
> Excellent! I've accepted and pushed all the commits. Thanks.
>
>> Make sweet-filter script more resistant to differences in Guile version.
>
> Tha
> New bundle time!
Awesome!
> First bundle: 2012-07-11-almkglor-comment-only.bundle - just
> additional comments, plus a no-op change in modern.scm (a bugfix in a
> part of the code that never gets called anyway)
All in.
> Second bundle: 2012-07-11-almkglor-SPLIT.bundle - dependent on first
> b
New bundle time!
First bundle: 2012-07-11-almkglor-comment-only.bundle - just
additional comments, plus a no-op change in modern.scm (a bugfix in a
part of the code that never gets called anyway)
commit f89889aadecf2ae3399cb66c0921852c120613ef
Author: Alan Manuel K. Gloria
Date: Wed Jul 11 22:
Alan Manuel Gloria
> Have a new bundle - this is dependent on the earlier bundle.
Excellent! I've accepted and pushed all the commits. Thanks.
> Make sweet-filter script more resistant to differences in Guile version.
Thanks. It looks odd, but I don't know of a better way to do it.
BTW,
Have a new bundle - this is dependent on the earlier bundle.
commit 4386c6906018a1f93b6c35a0233daf7ea32cb805
Author: Alan Manuel K. Gloria
Date: Tue Jul 10 15:09:36 2012 +0800
Added example partial implementation of SRFI-41 in example directory
commit 87652a41499a08e8642c05384dbdb6079bc08
Log:
commit 2f1ac5b303a15655e9f2c89656b7348119ad7a9f
Author: Alan Manuel K. Gloria
Date: Tue Jul 10 13:45:57 2012 +0800
Reimplement primitive-load replacement.
commit f5dd789be7ce12e6776ae3e789ed682ef2870431
Author: Alan Manuel K. Gloria
Date: Tue Jul 10 12:27:33 2012 +0800
Added
82 matches
Mail list logo
