- metatilities-devel@lists.common-lisp.net

[Metatilities-devel] ECL Build Fix
by Brit Butler 31 Oct '09

31 Oct '09

Dear devs, ECL cannot currently build metatilities due to some strange interaction with generic-lisp.lisp. I have added a #-ecl reader conditional to the "port" module in metatilities.asd to resolve this issue. Please consider changing it upstream or looking into the issue further. I'm happy to help test. Thanks, Brit Butler

1 0

[Metatilities-devel] ECL Build Fix
by Brit Butler 31 Oct '09

31 Oct '09

Dear devs, ECL cannot currently build metatilities due to some strange interaction with generic-lisp.lisp. I have added a #-ecl reader conditional to the "port" module in metatilities.asd to resolve this issue. Please consider changing it upstream or looking into the issue further. I'm happy to help test. Thanks, Brit Butler

1 0

Re: [Metatilities-devel] One more bug
by Gary King 04 Dec '08

04 Dec '08

Hi Gustavo, I just updated metatilities to 0.6.17 with the fix for this problem. Sorry it took so long and please do keep sending me problem reports and suggestions. thanks, On Nov 25, 2008, at 8:53 PM, Gustavo wrote: > Oh, a long time, I see. :) > > I use your stuff a lot, so it is likelly that I find bugs in it. > > 2008/11/25 Gary King <gwking(a)metabang.com> > Hi Gustavo > > Thanks for the detailed report. I haven't looked at (or even used!) > this code for a _long_ time so it wouldn't surprise me if its > broken. I'll see what I can do over the Thanksgiving break. > > regards, > > On Nov 25, 2008, at 7:51 PM, Gustavo wrote: > >> The compiler macros for functions disjoin and conjoin are broken. >> For debugging purposes, I copied the code to a macro to see what >> was happening. >> >> cl-user> (in-package :metatilities) >> #<package "METABANG.UTILITIES"> >> utilities> (defmacro disjoin* (&whole form &rest fns) >> (cond ((every #'(lambda (x) (or (symbolp x) (function-expression- >> p x))) fns) >> (with-unique-names (args) >> `#'(lambda (,args) >> (or ,@(mapcar #'(lambda (x) >> `(apply ,(extract-head-form x) >> ,args)) >> fns))))) >> (t form))) >> disjoin* >> utilities> (macroexpand-1 '(disjoin* #'macro-char-p #'whitespace-p)) >> #'(lambda (#:|args/1399|) >> (or (apply macro-char-p #:|args/1399|) (apply whitespace-p #:| >> args/1399|))) >> t >> >> I realized this bug trying to compile a function - sbcl complained >> about the variables macro-char-p and whitespace-p not to be >> defined. That makes me wonder: what is "extract-head-form" doing? >> It should be usefull only if you did something like: >> >> (define-compiler-macro disjoin (fn &rest fns) >> ... >> `(,(extract-head-form x) ,@args) >> ... >> ) >> >> I.e., eliminating the funcalls (I saw that somewhere on cliki.net >> some time ago).And, by the way, I guess that, the way the function >> disjoin is being defined, I guess there is no way to do this (the >> argument list is only known in execution time). > > -- > Gary Warren King, metabang.com > Cell: (413) 559 8738 > Fax: (206) 338-4052 > gwkkwg on Skype * garethsan on AIM > > > > > -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

Re: [Metatilities-devel] One more bug
by Gary King 26 Nov '08

26 Nov '08

Hi Gustavo Thanks for the detailed report. I haven't looked at (or even used!) this code for a _long_ time so it wouldn't surprise me if its broken. I'll see what I can do over the Thanksgiving break. regards, On Nov 25, 2008, at 7:51 PM, Gustavo wrote: > The compiler macros for functions disjoin and conjoin are broken. > For debugging purposes, I copied the code to a macro to see what was > happening. > > cl-user> (in-package :metatilities) > #<package "METABANG.UTILITIES"> > utilities> (defmacro disjoin* (&whole form &rest fns) > (cond ((every #'(lambda (x) (or (symbolp x) (function-expression-p > x))) fns) > (with-unique-names (args) > `#'(lambda (,args) > (or ,@(mapcar #'(lambda (x) > `(apply ,(extract-head-form x) > ,args)) > fns))))) > (t form))) > disjoin* > utilities> (macroexpand-1 '(disjoin* #'macro-char-p #'whitespace-p)) > #'(lambda (#:|args/1399|) > (or (apply macro-char-p #:|args/1399|) (apply whitespace-p #:| > args/1399|))) > t > > I realized this bug trying to compile a function - sbcl complained > about the variables macro-char-p and whitespace-p not to be defined. > That makes me wonder: what is "extract-head-form" doing? It should > be usefull only if you did something like: > > (define-compiler-macro disjoin (fn &rest fns) > ... > `(,(extract-head-form x) ,@args) > ... > ) > > I.e., eliminating the funcalls (I saw that somewhere on cliki.net > some time ago).And, by the way, I guess that, the way the function > disjoin is being defined, I guess there is no way to do this (the > argument list is only known in execution time). -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[Metatilities-devel] Re: Problem with metatilities
by Gary King 26 Jun '07

26 Jun '07

(reply sent to list as well) Hi Arthur, Thanks again for pointing out this problem. I've just updated metatilities on the web with a fix for the missing copy-stream. I have no idea what happened to it and neither does darcs. Please let me know if Tinaa still complains about anything. -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[Metatilities-devel] Announcing: Metatilities 0.6.8
by Gary King 26 Jun '07

26 Jun '07

##### Metatilities 0.6.8 Finally, [Metatilities][] corrects docstrings to be CL-Markdown compliant, fixes an ASDF system definition missing dependency and returns the mysteriously missing copy-stream (whose implementation I borrow from ASDF-Install). I don't know how this ever worked and I hate it when tat happens. More excitingly, I've moved some generic file handling macros from CL-Markdown to metatilities including: [with-input][], [with-output][], and [with-stream-from-specifier][]. More information on them will appear in a Common Lisp related weblog near you! [with-stream-from-specifier]: http://common-lisp.net/project/cl- containers/metatilities/documentation/metabang.utilities-package/ macro-with--stream--from--specifier.html [with-output]: http://common-lisp.net/project/cl-containers/ metatilities/documentation/metabang.utilities-package/macro-with-- output.html [with-input]: http://common-lisp.net/project/cl-containers/ metatilities/documentation/metabang.utilities-package/macro-with-- input.html [CL-Markdown]: http://common-lisp.net/project/cl-markdown/ [CL-Containers]: http://common-lisp.net/project/cl-containers/ [CL-Graph]: http://common-lisp.net/project/cl-graph/ [CL-Mathstats]: http://common-lisp.net/project/cl-mathstats/ [CL-variates]: http://common-lisp.net/project/cl-variates/ [metatilities]: http://common-lisp.net/project/metatilities/ -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[Metatilities-devel] [Announce]: Metatilities to 0.6.3
by Gary King 15 Feb '07

15 Feb '07

Thanks to Luke Cook for pointing out that I'd muffed the package machinations for combining [CL-FAD][] with [Metatilities][]. Version 0.6.3 corrects this and switches the system dependencies to keywords instead of symbols in the hopes of making "system not found" errors less inexplicable. [Metatilities]: http://common-lisp.net/project/metatilities/ [CL-FAD]: http://www.cliki.net/CL-FAD -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[Metatilities-devel] Auto-nag: metatilities please update your webpage
by root＠common-lisp.net 05 Feb '07

05 Feb '07

You are being nagged on because you have not created a sensible default webpage for your project. Please do so or you will be nagged again next week. All we ask is that you type in something about the project and perhaps some links to mailinglists etc. See common-lisp.net/project/clo/sp/index.html for a reasonable template. Some projects host their webpages somewhere else (eg. http://common-lisp.net/project/cl-ppcre) and if you're in the same situation you may put the following in your index.shtml: <HTML> <HEAD> <META HTTP-EQUIV="refresh" CONTENT="0;URL=YOURURLGOESHERE"> </HEAD> <BODY> </BODY> </HTML> Any questions? You can reach the author of this cronjob at clo-devel(a)common-lisp.net Thanks!

1 0

[Metatilities-devel] Auto-nag: metatilities please update your webpage
by root＠common-lisp.net 29 Jan '07

29 Jan '07

You are being nagged on because you have not created a sensible default webpage for your project. Please do so or you will be nagged again next week. All we ask is that you type in something about the project and perhaps some links to mailinglists etc. See common-lisp.net/project/clo/sp/index.html for a reasonable template. Some projects host their webpages somewhere else (eg. http://common-lisp.net/project/cl-ppcre) and if you're in the same situation you may put the following in your index.shtml: <HTML> <HEAD> <META HTTP-EQUIV="refresh" CONTENT="0;URL=YOURURLGOESHERE"> </HEAD> <BODY> </BODY> </HTML> Any questions? You can reach the author of this cronjob at clo-devel(a)common-lisp.net Thanks!

1 0

[Metatilities-devel] Auto-nag: metatilities please update your webpage
by root＠common-lisp.net 22 Jan '07

22 Jan '07

You are being nagged on because you have not created a sensible default webpage for your project. Please do so or you will be nagged again next week. All we ask is that you type in something about the project and perhaps some links to mailinglists etc. See common-lisp.net/project/clo/sp/index.html for a reasonable template. Some projects host their webpages somewhere else (eg. http://common-lisp.net/project/cl-ppcre) and if you're in the same situation you may put the following in your index.shtml: <HTML> <HEAD> <META HTTP-EQUIV="refresh" CONTENT="0;URL=YOURURLGOESHERE"> </HEAD> <BODY> </BODY> </HTML> Any questions? You can reach the author of this cronjob at clo-devel(a)common-lisp.net Thanks!

1 0