From evrim at core.gen.tr  Sun Feb  4 17:45:16 2007
From: evrim at core.gen.tr (Evrim ULU)
Date: Sun, 04 Feb 2007 19:45:16 +0200
Subject: [Bese-devel] custom yaclml and deftag-macro
Message-ID: <45C61BAC.9010804@core.gen.tr>

Hi,

It seems tags defines via deftag-macro does not accept custom attributes
provided with (@ ...) . Are there any workarounds to keep things standard?

evrim.


From attila.lendvai at gmail.com  Sun Feb  4 17:59:34 2007
From: attila.lendvai at gmail.com (Attila Lendvai)
Date: Sun, 4 Feb 2007 18:59:34 +0100
Subject: [Bese-devel] custom yaclml and deftag-macro
In-Reply-To: <45C61BAC.9010804@core.gen.tr>
References: <45C61BAC.9010804@core.gen.tr>
Message-ID: <b54b34af0702040959y2c117791m7f472b67a5909358@mail.gmail.com>

> Hi,

hi Evrim,

> It seems tags defines via deftag-macro does not accept custom attributes
> provided with (@ ...) . Are there any workarounds to keep things standard?

i'm not sure what you mean with standard, but i hope the enclosed
patch helps. it's a cleanup of the (@ ...) stuff, the patch
description:

Tue Jan 30 20:00:37 CET 2007  attila.lendvai at gmail.com
  * Added &allow-custom-attributes and cleaned up handling of the (@
...) attribute syntax

  Now &allow-other-attributes implies &allow-custom-attributes and the
other-attrbiute-list
  also contains the custom attrbiutes. Propagating custom attributes
e.g. from <ucw:input to
  <:input is now possible by adding an extra (@ ,others) entry.

  Also changed the internal representation other attributes from list
of cons to setf-like
  list of pairs.

i didn't push it yet, because i wanted to test it further to see if
anything breaks and iirc it needs some small changes in ucw here and
there. but i didn't want to touch the ucw repos not to create extra
work for Drew with non-essention patches.

hth,

-- 
- attila

"- The truth is that I've been too considerate, and so became
unintentionally cruel...
 - I understand.
 - No, you don't understand! We don't speak the same language!"
(Ingmar Bergman - Smultronst?llet)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: yaclml-custom-attrs.patch.gz
Type: application/x-gzip
Size: 6607 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20070204/4f5eadf5/attachment.bin>

From attila.lendvai at gmail.com  Sun Feb  4 23:51:45 2007
From: attila.lendvai at gmail.com (Attila Lendvai)
Date: Mon, 5 Feb 2007 00:51:45 +0100
Subject: [Bese-devel] custom yaclml and deftag-macro
In-Reply-To: <45C62CE0.5030803@core.gen.tr>
References: <45C61BAC.9010804@core.gen.tr>
	<b54b34af0702040959y2c117791m7f472b67a5909358@mail.gmail.com>
	<45C62CE0.5030803@core.gen.tr>
Message-ID: <b54b34af0702041551r7da3d69ci20436a4670d942ce@mail.gmail.com>

> I've applied it somehow. Here is what i get:

sorry, i've issued the "darcs send" towards the wrong repo. this patch
should apply fine after gunzip'ped.

YACLML> (deftag-macro x (&attribute xyz &allow-other-attributes others)
          `(<:input :name ,xyz (@ , at others)))
X
YACLML> (x :xyz 42 :type "alma" :foo "bar" (@ 88 77))
<input name="42" type="alma" foo="bar" 88="77"
/>
; No value

> It drops others and custom. Could you explain how to use this properly?

i knew something is still not ok with it... :)

unfortunately this patch temporarily drops the ability to use runtime
attribute lists with (@ list-var-name) i'll readd it later when i find
out how. the new syntax will probably also change to (* var1 var2 ...)
i don't think many people use it, but comments are welcome!

please unpull the previous patch before applying this one.

-- 
- attila

"- The truth is that I've been too considerate, and so became
unintentionally cruel...
 - I understand.
 - No, you don't understand! We don't speak the same language!"
(Ingmar Bergman - Smultronst?llet)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: yaclml-custom-cleanup2.patch.gz
Type: application/x-gzip
Size: 7198 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20070205/74c0f796/attachment.bin>

From evrim at core.gen.tr  Mon Feb  5 09:36:00 2007
From: evrim at core.gen.tr (Evrim ULU)
Date: Mon, 05 Feb 2007 11:36:00 +0200
Subject: [Bese-devel] custom yaclml and deftag-macro
In-Reply-To: <b54b34af0702041551r7da3d69ci20436a4670d942ce@mail.gmail.com>
References: <45C61BAC.9010804@core.gen.tr>	<b54b34af0702040959y2c117791m7f472b67a5909358@mail.gmail.com>	<45C62CE0.5030803@core.gen.tr>
	<b54b34af0702041551r7da3d69ci20436a4670d942ce@mail.gmail.com>
Message-ID: <45C6FA80.2020008@core.gen.tr>

Attila Lendvai wrote:

>> I've applied it somehow. Here is what i get:
>
>
> sorry, i've issued the "darcs send" towards the wrong repo. this patch
> should apply fine after gunzip'ped.
>
> YACLML> (deftag-macro x (&attribute xyz &allow-other-attributes others)
>          `(<:input :name ,xyz (@ , at others)))
> X
> YACLML> (x :xyz 42 :type "alma" :foo "bar" (@ 88 77))
> <input name="42" type="alma" foo="bar" 88="77"
> />
> ; No value

Ok this works. I have a request since the current situation breaks older macros.  it's very time consuming to fix old codes as you know.

It would be better if we can have something like:

(deftag-macro x (&attribute xyz &allow-other-attributes others &allow-custom-attributes custom)
 `(<:input (@ , at custom) :name ,xyz ,others))

I'm happy with the @ sign btw, why did you think to change it to *?

Thanks.
evrim.



From attila.lendvai at gmail.com  Mon Feb  5 11:43:24 2007
From: attila.lendvai at gmail.com (Attila Lendvai)
Date: Mon, 5 Feb 2007 12:43:24 +0100
Subject: [Bese-devel] custom yaclml and deftag-macro
In-Reply-To: <45C6FA80.2020008@core.gen.tr>
References: <45C61BAC.9010804@core.gen.tr>
	<b54b34af0702040959y2c117791m7f472b67a5909358@mail.gmail.com>
	<45C62CE0.5030803@core.gen.tr>
	<b54b34af0702041551r7da3d69ci20436a4670d942ce@mail.gmail.com>
	<45C6FA80.2020008@core.gen.tr>
Message-ID: <b54b34af0702050343l5b2d2ae8v2562707c01aff22c@mail.gmail.com>

> Ok this works. I have a request since the current situation breaks older macros.  it's very time consuming to fix old codes as you know.
>
> It would be better if we can have something like:
>
> (deftag-macro x (&attribute xyz &allow-other-attributes others &allow-custom-attributes custom)
>  `(<:input (@ , at custom) :name ,xyz ,others))

that should be , at others, but read below.

we have a choice here:

- currently OTHERS also contain the CUSTOM attributes when
&allow-other-attributes is given. this simplifies using
&allow-other-attributes, but it also means that "SomE" non-keyword
attribute names can appear in the OTHERS list, so you can't simply
, at OTHERS, but have to (@ , at OTHERS) to propagate the attributes to the
inner tag.

- this could be dropped and OTHERS/CUSTOMS separated and then , at OTHERS
were safe for the simple , at OTHERS, but then you would have to deal
with &allow-custom-attributes separately with an additional (@
, at CUSTOMS)  if you want to allow custom attributes. imho this is
cumbersome most of the time. i think most of the time you just want to
specify that you allow other attributes to disable the warnings, and
you don't care if they will be specified as keyword attrs or custom
attrs.

that's why i've decided for the former which is implemented currently.
but i think it's compatible with the old code as long as you don't use
custom attributes but they didn't exist before so i think it should be
backwards compatible.

> I'm happy with the @ sign btw, why did you think to change it to *?

you missed an important detail, before the patch

(let ((x '("foo" 42))
  (<:bar (@ x) :some "other"))

was taking the attribute list found in X _at runtime_, which i think
is different enough to deserve a different notation. i've proposed (*
x var2 ...) for that.

hth,

-- 
- attila

"- The truth is that I've been too considerate, and so became
unintentionally cruel...
 - I understand.
 - No, you don't understand! We don't speak the same language!"
(Ingmar Bergman - Smultronst?llet)

From evrim at core.gen.tr  Mon Feb  5 12:05:49 2007
From: evrim at core.gen.tr (Evrim ULU)
Date: Mon, 05 Feb 2007 14:05:49 +0200
Subject: [Bese-devel] custom yaclml and deftag-macro
In-Reply-To: <b54b34af0702050343l5b2d2ae8v2562707c01aff22c@mail.gmail.com>
References: <45C61BAC.9010804@core.gen.tr>	
	<b54b34af0702040959y2c117791m7f472b67a5909358@mail.gmail.com>	
	<45C62CE0.5030803@core.gen.tr>	
	<b54b34af0702041551r7da3d69ci20436a4670d942ce@mail.gmail.com>	
	<45C6FA80.2020008@core.gen.tr>
	<b54b34af0702050343l5b2d2ae8v2562707c01aff22c@mail.gmail.com>
Message-ID: <45C71D9D.9090907@core.gen.tr>

Attila Lendvai wrote:

>> Ok this works. I have a request since the current situation breaks
>> older macros.  it's very time consuming to fix old codes as you know.
>>
>> It would be better if we can have something like:
>>
>> (deftag-macro x (&attribute xyz &allow-other-attributes others
>> &allow-custom-attributes custom)
>>  `(<:input (@ , at custom) :name ,xyz ,others))
>
>
pasting from attribute-bind:

          ,(when body-var
              `(setf ,body-var ,attribute-values))
;;            ,(when other-attributes
;;               `(setf ,other-attributes (append (nreverse
,other-attributes) ,custom-attributes)))
           ,@(if (and (consp body)
                      (consp (car body))

Commenting above lines did what i want. I only need to do nreverse over
other-attributes. The evalutation problem may be solved by making (list
, at custom) so that the inside variables of the custom is evaluated before
going into tags.

> that should be , at others, but read below.
>
> we have a choice here:
>
> - currently OTHERS also contain the CUSTOM attributes when
> &allow-other-attributes is given. this simplifies using
> &allow-other-attributes, but it also means that "SomE" non-keyword
> attribute names can appear in the OTHERS list, so you can't simply
> , at OTHERS, but have to (@ , at OTHERS) to propagate the attributes to the
> inner tag.
>
> - this could be dropped and OTHERS/CUSTOMS separated and then , at OTHERS
> were safe for the simple , at OTHERS, but then you would have to deal
> with &allow-custom-attributes separately with an additional (@
> , at CUSTOMS)  if you want to allow custom attributes. imho this is
> cumbersome most of the time. i think most of the time you just want to
> specify that you allow other attributes to disable the warnings, and
> you don't care if they will be specified as keyword attrs or custom
> attrs.
>
> that's why i've decided for the former which is implemented currently.
> but i think it's compatible with the old code as long as you don't use
> custom attributes but they didn't exist before so i think it should be
> backwards compatible.


My inner feelings tell me that if others imply custom, macros using
macros would fail since other attributes are passed directly as custom
attributes. So keeping them seperate would bless us and keep us away
from these kinds of bugs.

Breaking the backward compatilbity would lead confusion among users.
This is more important i think.

>> I'm happy with the @ sign btw, why did you think to change it to *?
>
>
> you missed an important detail, before the patch
>
> (let ((x '("foo" 42))
>  (<:bar (@ x) :some "other"))
>
> was taking the attribute list found in X _at runtime_, which i think
> is different enough to deserve a different notation. i've proposed (*
> x var2 ...) for that.
>
Hm does that mean a second sign to use like (* '(foo 42))? If it is,
that's ok with me.

Comments on the overall situation:

The attribute-bind macro is bloated. I really don't like the hash table
approach (*expander-..*), if i have time i want to change deftag and
deftag-macros to generate real macro to parse attributes so that we get
rid of attribute-bind. It would be more efficient and easy to debug.

I admit i can't debug it now, 4+ levels of macro expanding is beyond my
and users imagination.

Comments?

Thanks.
evrim.



From mbaringer at common-lisp.net  Tue Feb  6 05:15:05 2007
From: mbaringer at common-lisp.net (Marco Baringer)
Date: Tue,  6 Feb 2007 00:15:05 -0500 (EST)
Subject: [Bese-devel] New patches to yaclml:  5-Feb-2007
Message-ID: <20070206051505.B634C9@common-lisp.net>


Sun Feb  4 18:31:11 EST 2007  attila.lendvai at gmail.com
  * FIX: small misuse of unwind-protect in the xml-syntax

    M ./src/yaclml.lisp -6 +7


An updated tarball of yaclml's source can be downloaded here:
http://common-lisp.net/project/bese/tarballs/yaclml-20070205.tar.gz

Darcsweb URL:
http://uncommon-web.com/darcsweb/darcsweb.cgi?r=yaclml;a=summary


From daniel at sentivision.com  Wed Feb  7 10:28:16 2007
From: daniel at sentivision.com (Daniel Janus)
Date: Wed, 7 Feb 2007 11:28:16 +0100
Subject: [Bese-devel] REGEXP-DISPATCHER not binding the registers
Message-ID: <200702071128.16408.daniel@sentivision.com>

Hello,

Here is an excerpt from the documentation of REGEXP-DISPATCHER macro:

   Any registers in URL-REGEXP are available through the array bound
   to *dispatcher-registers*.

Unfortunately, it doesn't do that; the registers are lost on the way from
regexp-url-matcher to the dispatcher handler.

I worked around this by specializing my own handler on ENTRY-POINT-HANDLER
like this:

(defclass regexp-binding-handler (ucw::entry-point-handler)
  ())

(defmethod ucw::handler-handle ((handler regexp-binding-handler)
                                (application standard-application)
                                (context ucw::standard-request-context)
                                matcher-result)
  (let ((*dispatcher-registers* (cadr matcher-result)))
    (call-next-method)))

(defclass regexp-binding-dispatcher 
    (ucw::abstract-dispatcher ucw::regexp-url-matcher 
     regexp-binding-handler)
  ())

(defmacro regexp-binding-dispatcher (url-regexp &body body)
  "Unlike UCW's REGEXP-DISPATCHER, this dispatcher _really_ binds
the registers in URL-REGEXP to *dispatcher-registers*."
  `(make-instance 'regexp-binding-dispatcher
                  :url-string ,url-regexp
                  :handler (lambda ()
                             (with-call/cc
                               (let ((self nil))
                                 , at body)))))

However, I feel that REGEXP-DISPATCHER should be specialized on
REGEXP-BINDING-HANDLER.  Could anyone check it and accordingly
merge with mainline?

Thanks,
-- 
(with-best-regards '(Daniel Janus)
   :of 'Sentivision)


From mbaringer at common-lisp.net  Fri Feb  9 05:00:13 2007
From: mbaringer at common-lisp.net (Marco Baringer)
Date: Fri,  9 Feb 2007 00:00:13 -0500 (EST)
Subject: [Bese-devel] New patches to arnesi_dev:  8-Feb-2007
Message-ID: <20070209050013.8C9576200D@common-lisp.net>


Thu Feb  8 17:31:24 EST 2007  attila.lendvai at gmail.com
  * Fix (encoding-keyword-to-native :us-ascii) on lispworks (hopefully, can't test it)

    M ./src/string.lisp -1 +1


An updated tarball of arnesi_dev's source can be downloaded here:
http://common-lisp.net/project/bese/tarballs/arnesi_dev-20070208.tar.gz

Darcsweb URL:
http://uncommon-web.com/darcsweb/darcsweb.cgi?r=arnesi_dev;a=summary


From rvanmelle at gmail.com  Fri Feb  9 13:06:40 2007
From: rvanmelle at gmail.com (Reid van Melle)
Date: Fri, 9 Feb 2007 14:06:40 +0100
Subject: [Bese-devel] YACLML: question about xml namespaces in attributes
	names
Message-ID: <62D1459F-A87D-4115-85B0-254419DEF4E8@gmail.com>

I haven't been at lisp for all that long, so perhaps I should have  
been able to figure this out myself... but here goes:

I'm using YACLML and parenscript for animated SVG generation and  
would really like to pass some namespace-scoped attributes names,  
specifically for some of the SVG macros.

For example, typical usage of SVG <use> tag is:

<use xlink:href="foo" x="50" ...>

The first problem is that neither the "href" or "xlink:href"  
attributes are listed for the <use> element; of course, this is very  
easy to fix.  However, I can't figure out how to pass this as a valid  
attribute name to the macro and have it recognized and output correctly.

I hope somebody can quickly point me in the right direction.

- Reid van Melle


From henrik at evahjelte.com  Fri Feb  9 14:26:42 2007
From: henrik at evahjelte.com (Henrik Hjelte)
Date: Fri, 09 Feb 2007 15:26:42 +0100
Subject: [Bese-devel] YACLML: question about xml namespaces in
	attributes names
In-Reply-To: <62D1459F-A87D-4115-85B0-254419DEF4E8@gmail.com>
References: <62D1459F-A87D-4115-85B0-254419DEF4E8@gmail.com>
Message-ID: <1171031202.18582.113.camel@trinidad>

On Fri, 2007-02-09 at 14:06 +0100, Reid van Melle wrote:
> I hope somebody can quickly point me in the right direction.
Not a detailed answer to you but a quick one: There have been others who
have made things with SVG and yaclml earlier, search the mailing list if
you haven't done so yet. And I think that Attila Lendvai made some
syntax to make attributes on the fly using the @ (at) sign?

Hope someone fills in more details for you. SVG animations sound nice!

This reminds me I have promised my wife to make an animated bird for her
page, but that will have to be with bitmaps I think. 

/Henrik Hjelte




From rvanmelle at gmail.com  Fri Feb  9 14:35:10 2007
From: rvanmelle at gmail.com (Reid van Melle)
Date: Fri, 9 Feb 2007 15:35:10 +0100
Subject: [Bese-devel] YACLML: question about xml namespaces in attributes
	names
In-Reply-To: <1171031202.18582.113.camel@trinidad>
References: <62D1459F-A87D-4115-85B0-254419DEF4E8@gmail.com>
	<1171031202.18582.113.camel@trinidad>
Message-ID: <00CCD2AB-0572-48B4-AE41-78A082370092@gmail.com>

Very funny... I just figured this out about five minutes before this  
very helpful response.

The @ stuff works great.  No more details required.

If I get something cool working, I'll be sure to post an update if  
there is any interest.

- Reid

On 9-Feb-07, at 3:26 PM, Henrik Hjelte wrote:

> On Fri, 2007-02-09 at 14:06 +0100, Reid van Melle wrote:
>> I hope somebody can quickly point me in the right direction.
> Not a detailed answer to you but a quick one: There have been  
> others who
> have made things with SVG and yaclml earlier, search the mailing  
> list if
> you haven't done so yet. And I think that Attila Lendvai made some
> syntax to make attributes on the fly using the @ (at) sign?
>
> Hope someone fills in more details for you. SVG animations sound nice!
>
> This reminds me I have promised my wife to make an animated bird  
> for her
> page, but that will have to be with bitmaps I think.
>
> /Henrik Hjelte
>
>



From evrim at core.gen.tr  Fri Feb  9 18:37:16 2007
From: evrim at core.gen.tr (Evrim ULU)
Date: Fri, 09 Feb 2007 20:37:16 +0200
Subject: [Bese-devel] interesting
Message-ID: <45CCBF5C.6000502@core.gen.tr>

document.write(str.replace(/icrosof/g, "void"))

how to write this in parenscript? any ideas?

thnx.
evrim.



From henrik at evahjelte.com  Sat Feb 10 10:10:25 2007
From: henrik at evahjelte.com (Henrik Hjelte)
Date: Sat, 10 Feb 2007 11:10:25 +0100
Subject: [Bese-devel] interesting
In-Reply-To: <45CCBF5C.6000502@core.gen.tr>
References: <45CCBF5C.6000502@core.gen.tr>
Message-ID: <1171102225.18582.120.camel@trinidad>

On Fri, 2007-02-09 at 20:37 +0200, Evrim ULU wrote:
> document.write(str.replace(/icrosof/g, "void"))
> 
> how to write this in parenscript? any ideas?
> 
> thnx.
> evrim.
> 

JS> (js:js-to-string 
     '(document.write (str.replace (regex "/icrosof/g") "void")))

"document.write(str.replace(/icrosof/g, 'void'))"

or: 

JS> (js:js-to-string 
'(document.write ((slot-value str 'replace) 
                  (regex "/icrosof/g")
                  "void")))
"document.write(str.replace(/icrosof/g, 'void'))"

/Henrik Hjelte




From mbaringer at common-lisp.net  Sun Feb 11 05:15:07 2007
From: mbaringer at common-lisp.net (Marco Baringer)
Date: Sun, 11 Feb 2007 00:15:07 -0500 (EST)
Subject: [Bese-devel] New patches to yaclml: 10-Feb-2007
Message-ID: <20070211051507.2593B5200E@common-lisp.net>


Sat Feb 10 16:16:49 EST 2007  attila.lendvai at gmail.com
  * Added xml and xlink namespaces to *uri-to-package*

    M ./src/packages.lisp -3 +6
    M ./src/tags/svg.lisp +1
    M ./src/tal/compile.lisp -2 +8

Sat Feb 10 16:09:17 EST 2007  attila.lendvai at gmail.com
  * Fix <:embed, allow any kind of attribute

    M ./src/tags/html4.lisp -5 +2


An updated tarball of yaclml's source can be downloaded here:
http://common-lisp.net/project/bese/tarballs/yaclml-20070210.tar.gz

Darcsweb URL:
http://uncommon-web.com/darcsweb/darcsweb.cgi?r=yaclml;a=summary


From vagif at cox.net  Sat Feb 17 02:18:32 2007
From: vagif at cox.net (Vagif Verdi)
Date: Fri, 16 Feb 2007 18:18:32 -0800
Subject: [Bese-devel] Error in worker loop: "/" is not of type CHARACTER.
Message-ID: <20070217021838.OSRQ1349.fed1rmmtao103.cox.net@fed1rmimpo01.cox.net>

Windows, Lispworks 4.4.6, latest ucw-boxset.

After removing 18n application starts ok.

But trying to access page gives following error:

 

18:13 UCW.BACKEND/+ERROR+: Error in worker loop: "/" is not of type
CHARACTER..

18:13 UCW.BACKEND/+ERROR+: Worker thread #<IT.BESE.UCW::HTTPD-WORKER
21A229E4> reported #<TYPE-ERROR 20693AB4>.

18:13 UCW.BACKEND/+ERROR+: Error in worker loop: "/favicon.ico" is not of
type CHARACTER..

18:13 UCW.BACKEND/+ERROR+: Worker thread #<IT.BESE.UCW::HTTPD-WORKER
21A22B5C> reported #<TYPE-ERROR 21A84754>.

 

Same thing trying to point to index.ucw

 

18:14 UCW.BACKEND/+ERROR+: Error in worker loop: "/index.ucw" is not of type
CHARACTER..

18:14 UCW.BACKEND/+ERROR+: Worker thread #<IT.BESE.UCW::HTTPD-WORKER
21A22C84> reported #<TYPE-ERROR 21AAD53C>.

 

Regards,

Vagif

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20070216/6d1a95c0/attachment.html>

From mbaringer at common-lisp.net  Mon Feb 19 05:30:15 2007
From: mbaringer at common-lisp.net (Marco Baringer)
Date: Mon, 19 Feb 2007 00:30:15 -0500 (EST)
Subject: [Bese-devel] New patches to ucw_dev: 18-Feb-2007
Message-ID: <20070219053015.A3F7D7E005@common-lisp.net>


Sun Feb 18 09:22:37 EST 2007  attila.lendvai at gmail.com
  * Fix make-temp-filename, which fixes multiple uploads in a form. Upload needs further cleanups.

    M ./src/backend/common.lisp -1 +1


An updated tarball of ucw_dev's source can be downloaded here:
http://common-lisp.net/project/ucw/tarballs/ucw_dev-20070218.tar.gz

Darcsweb URL:
http://uncommon-web.com/darcsweb/darcsweb.cgi?r=ucw_dev;a=summary


From mbaringer at common-lisp.net  Mon Feb 19 05:30:15 2007
From: mbaringer at common-lisp.net (Marco Baringer)
Date: Mon, 19 Feb 2007 00:30:15 -0500 (EST)
Subject: [Bese-devel] New patches to ucw_ajax: 18-Feb-2007
Message-ID: <20070219053015.ADBFF7E003@common-lisp.net>


Sun Feb 18 09:22:37 EST 2007  attila.lendvai at gmail.com
  * Fix make-temp-filename, which fixes multiple uploads in a form. Upload needs further cleanups.

    M ./src/backend/common.lisp -1 +1


An updated tarball of ucw_ajax's source can be downloaded here:
http://common-lisp.net/project/ucw/tarballs/ucw_ajax-20070218.tar.gz

Darcsweb URL:
http://uncommon-web.com/darcsweb/darcsweb.cgi?r=ucw_ajax;a=summary


From attila.lendvai at gmail.com  Mon Feb 26 16:36:33 2007
From: attila.lendvai at gmail.com (Attila Lendvai)
Date: Mon, 26 Feb 2007 17:36:33 +0100
Subject: [Bese-devel] (no subject)
In-Reply-To: <b54b34af0701040656u2cf66a2akfa62fdb550e37e1d@mail.gmail.com>
References: <Pine.GSO.4.58L0.0612271105580.25889@balu.sch.bme.hu>
	<b54b34af0701040656u2cf66a2akfa62fdb550e37e1d@mail.gmail.com>
Message-ID: <b54b34af0702260836m30281a27ibfef0e53ad0f3c22@mail.gmail.com>

> fyi, i've applied this locally and stuff seems to keep on working, but
> i'd better leave the pushing of this for someone with more experience
> with the walker...
>
> but if nothing happens for long enough i'll push it eventually,
> because it looks good for my uneducated eyes.

dear list,

as noone review this patch and it seems to be a useful piece of code
for my uneducated eyes, i've pushed it. diff is available at:
http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=bese-arnesi_dev;a=commitdiff;h=20061226165103-2e713-3f5d96630afed44f8e3f10cb893154b687f8e9f1.gz

i've been running stuff locally with this patch included and i didn't
notice any regression for the time passed.

-- 
- attila

"- The truth is that I've been too considerate, and so became
unintentionally cruel...
 - I understand.
 - No, you don't understand! We don't speak the same language!"
(Ingmar Bergman - Smultronst?llet)

From mbaringer at common-lisp.net  Tue Feb 27 05:00:14 2007
From: mbaringer at common-lisp.net (Marco Baringer)
Date: Tue, 27 Feb 2007 00:00:14 -0500 (EST)
Subject: [Bese-devel] New patches to arnesi_dev: 26-Feb-2007
Message-ID: <20070227050014.80C235B06F@common-lisp.net>


Tue Dec 26 11:51:03 EST 2006  Berki Lukacs Tamas <blt at sch.bme.hu>
  * Evaluate macros in correct lexical environment in code walker, use code walking in sharpl-reader

    M ./arnesi.asd -1 +2
    M ./src/call-cc/interpreter.lisp -1 +1
    M ./src/lexenv.lisp -5 +298
    M ./src/sharpl-reader.lisp -19 +49
    M ./src/walk.lisp -42 +56
    A ./t/sharpl.lisp


An updated tarball of arnesi_dev's source can be downloaded here:
http://common-lisp.net/project/bese/tarballs/arnesi_dev-20070226.tar.gz

Darcsweb URL:
http://uncommon-web.com/darcsweb/darcsweb.cgi?r=arnesi_dev;a=summary