From scaekenberghe at common-lisp.net  Tue Apr  1 13:01:57 2008
From: scaekenberghe at common-lisp.net (Sven Van Caekenberghe)
Date: Tue, 1 Apr 2008 15:01:57 +0200
Subject: [postmodern-devel] Unexpected Result from SET command
Message-ID: <528A0189-F005-4816-82F8-3478A838B597@common-lisp.net>

Hi,

Is it possible that there is something wrong or missing in handling  
the result from a SET command ?

POSTMODERN 44 > (connect-toplevel "test" "postgres" "" "localhost")

POSTMODERN 45 > (execute "set time zone gmt")
CL-POSTGRES: set time zone gmt

Error: Postgresql protocol error: Unexpected message received: S
   1 (abort) Return to level 0.
   2 Return to top loop level 0.

Type :b for backtrace, :c <option number> to proceed,  or :? for other  
options

POSTMODERN 46 : 1 > :b
Call to CL-POSTGRES::LOOK-FOR-ROW
Call to CL-POSTGRES::SEND-QUERY
Call to (HARLEQUIN-COMMON-LISP:SUBFUNCTION (LABELS #:G135637) EXEC- 
QUERY)
Call to EXEC-QUERY
Call to EVAL
Call to CAPI::CAPI-TOP-LEVEL-FUNCTION
Call to CAPI::INTERACTIVE-PANE-TOP-LOOP
Call to (HARLEQUIN-COMMON-LISP:SUBFUNCTION MP::PROCESS-SG-FUNCTION  
MP::INITIALIZE-PROCESS-STACK)

Thanks,

Sven



From marijnh at gmail.com  Tue Apr  1 13:47:53 2008
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Tue, 1 Apr 2008 15:47:53 +0200
Subject: [postmodern-devel] Unexpected Result from SET command
In-Reply-To: <528A0189-F005-4816-82F8-3478A838B597@common-lisp.net>
References: <528A0189-F005-4816-82F8-3478A838B597@common-lisp.net>
Message-ID: <befaa7aa0804010647j6e64e17alecfc793ab727328a@mail.gmail.com>

Hey Sven,

>  POSTMODERN 45 > (execute "set time zone gmt")
>  CL-POSTGRES: set time zone gmt
>  Error: Postgresql protocol error: Unexpected message received: S

Oops - this was a case in the pg client/server protocol that I was not
handling correctly. I've pushed a patch which should solve the
problem.

Cheers,
Marijn


From scaekenberghe at common-lisp.net  Tue Apr  1 15:13:16 2008
From: scaekenberghe at common-lisp.net (Sven Van Caekenberghe)
Date: Tue, 1 Apr 2008 17:13:16 +0200
Subject: [postmodern-devel] Unexpected Result from SET command
In-Reply-To: <befaa7aa0804010647j6e64e17alecfc793ab727328a@mail.gmail.com>
References: <528A0189-F005-4816-82F8-3478A838B597@common-lisp.net>
	<befaa7aa0804010647j6e64e17alecfc793ab727328a@mail.gmail.com>
Message-ID: <BF4D227F-D1D8-41D7-9601-D64B1B7A0361@common-lisp.net>

Marijn,

On 01 Apr 2008, at 15:47, Marijn Haverbeke wrote:

> Hey Sven,
>
>> POSTMODERN 45 > (execute "set time zone gmt")
>> CL-POSTGRES: set time zone gmt
>> Error: Postgresql protocol error: Unexpected message received: S
>
> Oops - this was a case in the pg client/server protocol that I was not
> handling correctly. I've pushed a patch which should solve the
> problem.
>
> Cheers,
> Marijn

Pulling from "http://common-lisp.net/project/postmodern/darcs/ 
postmodern"...

Tue Apr  1 15:39:53 CEST 2008  marijnh at gmail.com
   * handle ParameterStatus messages when reading in query results

And it works for me now! Thanks a lot for the fast response.

Regards,

Sven




From marijnh at gmail.com  Wed Apr  9 18:42:57 2008
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Wed, 9 Apr 2008 20:42:57 +0200
Subject: [postmodern-devel] Release 1.11 [was: Unexpected Result from SET
	command]
Message-ID: <befaa7aa0804091142r72e22e5cwd6f407ca2ffdeaef@mail.gmail.com>

Hey list,

I've just released version 1.11 of Postmodern. Mostly bug-fixes, but
one feature to be careful with is the new auto-escaping: If you were
using 'true and 'false in your queries for boolean values, they will
now be escaped and not be read as boolean values at all, so use T and
NIL instead. See http://common-lisp.net/project/postmodern for a
slightly more detailed release description and, as always, the
darcsweb for the definite word on what happened.

Regards,
Marijn

On Tue, Apr 1, 2008 at 5:13 PM, Sven Van Caekenberghe
<scaekenberghe at common-lisp.net> wrote:
> Marijn,
>
>
>
>  On 01 Apr 2008, at 15:47, Marijn Haverbeke wrote:
>
>
> > Hey Sven,
> >
> >
> > > POSTMODERN 45 > (execute "set time zone gmt")
> > > CL-POSTGRES: set time zone gmt
> > > Error: Postgresql protocol error: Unexpected message received: S
> > >
> >
> > Oops - this was a case in the pg client/server protocol that I was not
> > handling correctly. I've pushed a patch which should solve the
> > problem.
> >
> > Cheers,
> > Marijn
> >
>
>  Pulling from
> "http://common-lisp.net/project/postmodern/darcs/postmodern"...
>
>  Tue Apr  1 15:39:53 CEST 2008  marijnh at gmail.com
>   * handle ParameterStatus messages when reading in query results
>
>  And it works for me now! Thanks a lot for the fast response.
>
>  Regards,
>
>
>
>  Sven
>
>
>  _______________________________________________
>  postmodern-devel mailing list
>  postmodern-devel at common-lisp.net
>  http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel
>


From info at jensteich.de  Mon Apr 14 12:59:10 2008
From: info at jensteich.de (Jens Teich)
Date: Mon, 14 Apr 2008 14:59:10 +0200
Subject: [postmodern-devel] s-sql insert-into problem
Message-ID: <C2435C3F-BA1E-4873-B219-0484DCB53A27@jensteich.de>

I have a tablename as string, a list of fieldnames as strings and a list
of values known only at runtime all.

Tried the following. What is going wrong?

HB> (sql
      (append
       (list :insert-into (intern "table") :set)
       (loop
	 for k in '("field1" "field2" "field3")
	 for v in '(4 5 6)
	 append (list (intern k) v))))

Error: Value (:INSERT-INTO |table| :SET |field1| 4 |field2| 5 |field3|  
6)
can not be converted to an SQL literal.
    [Condition of type SIMPLE-ERROR]

Jens


From marijnh at gmail.com  Mon Apr 14 13:05:21 2008
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Mon, 14 Apr 2008 15:05:21 +0200
Subject: [postmodern-devel] s-sql insert-into problem
In-Reply-To: <C2435C3F-BA1E-4873-B219-0484DCB53A27@jensteich.de>
References: <C2435C3F-BA1E-4873-B219-0484DCB53A27@jensteich.de>
Message-ID: <befaa7aa0804140605l54956418gbb6624cbd50a5d27@mail.gmail.com>

Hi Jens,

The expansion of SQL forms happens at macroexpansion time, while you
are building your query expression at run-time. Using SQL-COMPILE
where you now have SQL solves the problem.

Cheers,
Marijn


On Mon, Apr 14, 2008 at 2:59 PM, Jens Teich <info at jensteich.de> wrote:
> I have a tablename as string, a list of fieldnames as strings and a list
>  of values known only at runtime all.
>
>  Tried the following. What is going wrong?
>
>  HB> (sql
>      (append
>       (list :insert-into (intern "table") :set)
>       (loop
>          for k in '("field1" "field2" "field3")
>          for v in '(4 5 6)
>          append (list (intern k) v))))
>
>  Error: Value (:INSERT-INTO |table| :SET |field1| 4 |field2| 5 |field3| 6)
>  can not be converted to an SQL literal.
>    [Condition of type SIMPLE-ERROR]
>
>  Jens
>  _______________________________________________
>  postmodern-devel mailing list
>  postmodern-devel at common-lisp.net
>  http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel
>


From info at jensteich.de  Mon Apr 14 13:26:03 2008
From: info at jensteich.de (Jens Teich)
Date: Mon, 14 Apr 2008 15:26:03 +0200
Subject: [postmodern-devel] s-sql insert-into problem
In-Reply-To: <befaa7aa0804140605l54956418gbb6624cbd50a5d27@mail.gmail.com>
References: <C2435C3F-BA1E-4873-B219-0484DCB53A27@jensteich.de>
	<befaa7aa0804140605l54956418gbb6624cbd50a5d27@mail.gmail.com>
Message-ID: <6F553EBD-CECE-4BCF-88FF-CB1FB0BC73E0@jensteich.de>

Hi Marijn,

works like a charm.

Thanks for your great postmodern library.

Jens

Am 14.04.2008 um 15:05 schrieb Marijn Haverbeke:
> Hi Jens,
>
> The expansion of SQL forms happens at macroexpansion time, while you
> are building your query expression at run-time. Using SQL-COMPILE
> where you now have SQL solves the problem.
>
> Cheers,
> Marijn
>
>
> On Mon, Apr 14, 2008 at 2:59 PM, Jens Teich <info at jensteich.de> wrote:
>> I have a tablename as string, a list of fieldnames as strings and a  
>> list
>> of values known only at runtime all.
>>
>> Tried the following. What is going wrong?
>>
>> HB> (sql
>>     (append
>>      (list :insert-into (intern "table") :set)
>>      (loop
>>         for k in '("field1" "field2" "field3")
>>         for v in '(4 5 6)
>>         append (list (intern k) v))))
>>
>> Error: Value (:INSERT-INTO |table| :SET |field1| 4 |field2| 5 | 
>> field3| 6)
>> can not be converted to an SQL literal.
>>   [Condition of type SIMPLE-ERROR]
>>
>> Jens
>> _______________________________________________
>> postmodern-devel mailing list
>> postmodern-devel at common-lisp.net
>> http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel
>>
> _______________________________________________
> postmodern-devel mailing list
> postmodern-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel



From scaekenberghe at common-lisp.net  Mon Apr 14 13:32:45 2008
From: scaekenberghe at common-lisp.net (Sven Van Caekenberghe)
Date: Mon, 14 Apr 2008 15:32:45 +0200
Subject: [postmodern-devel] Timestamp (with time zone)
Message-ID: <AA1E014D-B3EA-4859-85E9-94D7448CCBA8@common-lisp.net>

Hi,

This is partly postmodern, partly postgresql related.

I was wondering whether it would not be useful to also do the  
following when loading simple-date above postmodern:

(in-package :simple-date)

(cl-postgres:set-sql-datetime-readers :timestamp-with-timezone (lambda  
(usecs)
    (multiple-value-bind (days usecs) (floor usecs +usecs-in-one-day+)
      (make-instance 'timestamp :days (+ days +postgres-day-offset+)
                     :ms (floor usecs 1000)))))

Or even in place of the normal :timestamp binding (from which the  
above code is copied) ?

 From my experiments and reading, using timestamp with time zone as  
SQL type is more useful than timestamp.

What I want is a created or last-modified timestamp that is set or  
updated automatically by SQL and not CL with a default like now(). The  
problem seems to be that the way now() is interpreted is dependent on  
the time zone set for the session (or the time zone default of  
postgresql, which defaults to your machine's).

The only correct thing to store are GMT timestamps and to adjust those  
to the viewer's own time zone. psql does that correctly only with the  
type timestamp with time zone and not with the type timestamp,  
although they seem to be the same thing internally.

In CL, (simple-date:universal-time-to-timestamp (get-universal-time))  
is always GMT, indepedent of the current (viewer's) timezone. In PG  
SQL this seems to be hard to do using now() or similar functions.

So out of the box reader support for that type would be useful.

A second question is how to correctly specify this col-type in a DAO  
since :timestamp-with-time-zone doesn't generate the necessary spaces  
when generating the table definition and a string is not considered a  
CL type ?

Any thoughts ?

Thanks,

Sven





  


From marijnh at gmail.com  Mon Apr 14 14:08:53 2008
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Mon, 14 Apr 2008 16:08:53 +0200
Subject: [postmodern-devel] Timestamp (with time zone)
In-Reply-To: <AA1E014D-B3EA-4859-85E9-94D7448CCBA8@common-lisp.net>
References: <AA1E014D-B3EA-4859-85E9-94D7448CCBA8@common-lisp.net>
Message-ID: <befaa7aa0804140708r20964861t398cdbc334295b7e@mail.gmail.com>

Hey Sven,

I had no idea now() behaves differently depending on the data type. I
can see the problem. There are two new patches in the repo, one adding
a reader for timestamp with time zone values as you suggested, and one
replacing dashes with spaces when writing out type names. That second
one is a bit of a hack, but seems to work well in most cases.

Cheers,
Marijn


On Mon, Apr 14, 2008 at 3:32 PM, Sven Van Caekenberghe
<scaekenberghe at common-lisp.net> wrote:
> Hi,
>
>  This is partly postmodern, partly postgresql related.
>
>  I was wondering whether it would not be useful to also do the following
> when loading simple-date above postmodern:
>
>  (in-package :simple-date)
>
>  (cl-postgres:set-sql-datetime-readers :timestamp-with-timezone (lambda
> (usecs)
>    (multiple-value-bind (days usecs) (floor usecs +usecs-in-one-day+)
>      (make-instance 'timestamp :days (+ days +postgres-day-offset+)
>                     :ms (floor usecs 1000)))))
>
>  Or even in place of the normal :timestamp binding (from which the above
> code is copied) ?
>
>  From my experiments and reading, using timestamp with time zone as SQL type
> is more useful than timestamp.
>
>  What I want is a created or last-modified timestamp that is set or updated
> automatically by SQL and not CL with a default like now(). The problem seems
> to be that the way now() is interpreted is dependent on the time zone set
> for the session (or the time zone default of postgresql, which defaults to
> your machine's).
>
>  The only correct thing to store are GMT timestamps and to adjust those to
> the viewer's own time zone. psql does that correctly only with the type
> timestamp with time zone and not with the type timestamp, although they seem
> to be the same thing internally.
>
>  In CL, (simple-date:universal-time-to-timestamp (get-universal-time)) is
> always GMT, indepedent of the current (viewer's) timezone. In PG SQL this
> seems to be hard to do using now() or similar functions.
>
>  So out of the box reader support for that type would be useful.
>
>  A second question is how to correctly specify this col-type in a DAO since
> :timestamp-with-time-zone doesn't generate the necessary spaces when
> generating the table definition and a string is not considered a CL type ?
>
>  Any thoughts ?
>
>  Thanks,
>
>  Sven
>
>
>
>
>
>  _______________________________________________
>  postmodern-devel mailing list
>  postmodern-devel at common-lisp.net
>  http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel
>


From scaekenberghe at common-lisp.net  Mon Apr 14 14:51:27 2008
From: scaekenberghe at common-lisp.net (Sven Van Caekenberghe)
Date: Mon, 14 Apr 2008 16:51:27 +0200
Subject: [SPAM] Re: [postmodern-devel] Timestamp (with time zone)
In-Reply-To: <befaa7aa0804140708r20964861t398cdbc334295b7e@mail.gmail.com>
References: <AA1E014D-B3EA-4859-85E9-94D7448CCBA8@common-lisp.net>
	<befaa7aa0804140708r20964861t398cdbc334295b7e@mail.gmail.com>
Message-ID: <BB6E9BC9-2FE0-48D1-9E9D-ECE57CFB0679@common-lisp.net>

Marijn,

On 14 Apr 2008, at 16:08, Marijn Haverbeke wrote:

> I had no idea now() behaves differently depending on the data type.
> I can see the problem.

Well, the documentation,

http://www.postgresql.org/docs/8.3/static/datatype-datetime.html

is quite confusing around these issues, it does seem to be possible to  
do extra conversions, but I would expect their now() to work like (get- 
universal-time), but I am no postgresql expert.

> There are two new patches in the repo, one adding
> a reader for timestamp with time zone values as you suggested, and one
> replacing dashes with spaces when writing out type names. That second
> one is a bit of a hack, but seems to work well in most cases.

Thanks for the patches, it now works for me.

Sven

PS:

I would like to add that Postmodern is a very nice project, well  
documented. I know from experience that this requires a lot of work. I  
was especially surprised (in the good way) by the quality of your  
source code: very readable, using many CL features in a clean way.  
Great work!



From scaekenberghe at common-lisp.net  Sat Apr 19 16:49:36 2008
From: scaekenberghe at common-lisp.net (Sven Van Caekenberghe)
Date: Sat, 19 Apr 2008 18:49:36 +0200
Subject: [postmodern-devel] Error when no persistent field
Message-ID: <03F9740A-AD2A-4085-8BE2-4B101F072E2B@common-lisp.net>

Hi,

I defined an object with metaclass dao-class but forgot to add any col- 
type options, this results in a rather cryptic error that is hard to  
get out of in LispWorks:

P1 10 > (select-dao 'enumeration)

Error: The assertion (= (LENGTH POSTMODERN::QUERY-FIELDS)  
POSTMODERN::N-DAO-FIELDS) failed.
  1 (continue) Retry assertion.
  2 (abort) Return to level 0.
  3 Return to top loop level 0.

Type :b for backtrace, :c <option number> to proceed,  or :? for other  
options

P1 11 : 1 > :bq

(HARLEQUIN-COMMON-LISP:SUBFUNCTION 1 POSTMODERN::BUILD-ROW-READER) <-  
CL-POSTGRES::SEND-QUERY
<- (HARLEQUIN-COMMON-LISP:SUBFUNCTION (LABELS #:G244377) CL- 
POSTGRES:EXEC-QUERY) <- CL-POSTGRES:EXEC-QUERY <- LET
<- EVAL <- CAPI::CAPI-TOP-LEVEL-FUNCTION <- CAPI::INTERACTIVE-PANE-TOP- 
LOOP
<- (HARLEQUIN-COMMON-LISP:SUBFUNCTION MP::PROCESS-SG-FUNCTION  
MP::INITIALIZE-PROCESS-STACK)

I can live with this, but maybe it would be good to make this more  
user friendly.

Cheers,

Sven


From marijnh at gmail.com  Sat Apr 19 17:29:02 2008
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Sat, 19 Apr 2008 19:29:02 +0200
Subject: [postmodern-devel] Error when no persistent field
In-Reply-To: <03F9740A-AD2A-4085-8BE2-4B101F072E2B@common-lisp.net>
References: <03F9740A-AD2A-4085-8BE2-4B101F072E2B@common-lisp.net>
Message-ID: <befaa7aa0804191029n13db5444j60503a5836d4840a@mail.gmail.com>

Good point. This and similar table-does-not-match-class errors are
bound to come up a lot, so I've added some more helpful error
messages.

Cheers,
Marijn

>  I defined an object with metaclass dao-class but forgot to add any col-type
> options, this results in a rather cryptic error that is hard to get out of
> in LispWorks:
>
>  P1 10 > (select-dao 'enumeration)
>
>  Error: The assertion (= (LENGTH POSTMODERN::QUERY-FIELDS)
> POSTMODERN::N-DAO-FIELDS) failed.
>   1 (continue) Retry assertion.
>   2 (abort) Return to level 0.
>   3 Return to top loop level 0.
>
>  Type :b for backtrace, :c <option number> to proceed,  or :? for other
> options
>
>  P1 11 : 1 > :bq
>
>  (HARLEQUIN-COMMON-LISP:SUBFUNCTION 1 POSTMODERN::BUILD-ROW-READER) <-
> CL-POSTGRES::SEND-QUERY
>  <- (HARLEQUIN-COMMON-LISP:SUBFUNCTION (LABELS #:G244377)
> CL-POSTGRES:EXEC-QUERY) <- CL-POSTGRES:EXEC-QUERY <- LET
>  <- EVAL <- CAPI::CAPI-TOP-LEVEL-FUNCTION <- CAPI::INTERACTIVE-PANE-TOP-LOOP
>  <- (HARLEQUIN-COMMON-LISP:SUBFUNCTION MP::PROCESS-SG-FUNCTION
> MP::INITIALIZE-PROCESS-STACK)
>
>  I can live with this, but maybe it would be good to make this more user
> friendly.
>
>  Cheers,
>
>  Sven
>  _______________________________________________
>  postmodern-devel mailing list
>  postmodern-devel at common-lisp.net
>  http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel
>


From scaekenberghe at common-lisp.net  Sun Apr 20 11:37:46 2008
From: scaekenberghe at common-lisp.net (Sven Van Caekenberghe)
Date: Sun, 20 Apr 2008 13:37:46 +0200
Subject: [postmodern-devel] Error when no persistent field
In-Reply-To: <befaa7aa0804191029n13db5444j60503a5836d4840a@mail.gmail.com>
References: <03F9740A-AD2A-4085-8BE2-4B101F072E2B@common-lisp.net>
	<befaa7aa0804191029n13db5444j60503a5836d4840a@mail.gmail.com>
Message-ID: <409B450A-6A73-4F5C-9E85-EA8FC9D4D129@common-lisp.net>


On 19 Apr 2008, at 19:29, Marijn Haverbeke wrote:

> Good point. This and similar table-does-not-match-class errors are
> bound to come up a lot, so I've added some more helpful error
> messages.

Thanks, did you also handle the case of using get-dao when there are  
no keys defined ? I believe that got into a loop...
There might be others too, but the more I get things right, the less  
absolute beginner errors that I make ;-)

Sven



From marijnh at gmail.com  Mon Apr 21 13:15:35 2008
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Mon, 21 Apr 2008 15:15:35 +0200
Subject: [postmodern-devel] Error when no persistent field
In-Reply-To: <409B450A-6A73-4F5C-9E85-EA8FC9D4D129@common-lisp.net>
References: <03F9740A-AD2A-4085-8BE2-4B101F072E2B@common-lisp.net>
	<befaa7aa0804191029n13db5444j60503a5836d4840a@mail.gmail.com>
	<409B450A-6A73-4F5C-9E85-EA8FC9D4D129@common-lisp.net>
Message-ID: <befaa7aa0804210615s55592e0csbc29fda5dc3fae40@mail.gmail.com>

Hi Sven,

>  Thanks, did you also handle the case of using get-dao when there are no
> keys defined ? I believe that got into a loop...

It did -- though some rather bizarre corner case. I've pushed a fix to
raise an error instead -- calling get-dao on key-less classes is not
allowed.

Regards,
Marijn


From scaekenberghe at common-lisp.net  Mon Apr 21 16:57:08 2008
From: scaekenberghe at common-lisp.net (Sven Van Caekenberghe)
Date: Mon, 21 Apr 2008 18:57:08 +0200
Subject: [postmodern-devel] Error when no persistent field
In-Reply-To: <befaa7aa0804210615s55592e0csbc29fda5dc3fae40@mail.gmail.com>
References: <03F9740A-AD2A-4085-8BE2-4B101F072E2B@common-lisp.net>
	<befaa7aa0804191029n13db5444j60503a5836d4840a@mail.gmail.com>
	<409B450A-6A73-4F5C-9E85-EA8FC9D4D129@common-lisp.net>
	<befaa7aa0804210615s55592e0csbc29fda5dc3fae40@mail.gmail.com>
Message-ID: <0C7CA4E3-522E-48F1-B2D5-FCB0FF0835BD@common-lisp.net>

Hi Marijn,

On 21 Apr 2008, at 15:15, Marijn Haverbeke wrote:

> Hi Sven,
>
>> Thanks, did you also handle the case of using get-dao when there  
>> are no
>> keys defined ? I believe that got into a loop...
>
> It did -- though some rather bizarre corner case. I've pushed a fix to
> raise an error instead -- calling get-dao on key-less classes is not
> allowed.
>
> Regards,
> Marijn

I know, catching these newbie errors is not the real stuff. I now get:

P1 24 > (defclass foo () ())
#<STANDARD-CLASS FOO 21F6D767>

P1 25 > (get-dao 'foo)

Error: Class FOO has no key slots.
  1 (abort) Return to level 0.
  2 Return to top loop level 0.

Type :b for backtrace, :c <option number> to proceed,  or :? for other  
options

This is certainly correct and better than a loop. However, in the  
above transcript I even forgot to declare the proper meta class, maybe  
that should be the first error being reported. I know I am being  
annoying, but I am only trying to help; I promise I will never repeat  
this suggestion. Next time, I'll hopefully have a better request.

Sven


From marijnh at gmail.com  Wed Apr 30 12:15:17 2008
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Wed, 30 Apr 2008 14:15:17 +0200
Subject: [postmodern-devel] Release 1.12
Message-ID: <befaa7aa0804300515h5a94e310r81f79382afbfd6ef@mail.gmail.com>

Hi list,

There is now a version 1.12 of postmodern. It features SSL support, a
few rather un-spectacular new features, and less bugs than 1.11. See
the docs and the darcsweb for details.

Regards,
Marijn