pllolcode - pllolcode: Improve string handling in lex scanner by - Mailing list pgsql-committers

From eggyknap@pgfoundry.org (User Eggyknap)
Subject pllolcode - pllolcode: Improve string handling in lex scanner by
Date
Msg-id 20080704010453.82CCA17AE71D@pgfoundry.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Improve string handling in lex scanner by liberally following plpgsql's example
Also fix bug in returning boolean values

Modified Files:
--------------
    pllolcode:
        pllolcode.c (r1.22 -> r1.23)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/pllolcode/pllolcode.c.diff?r1=1.22&r2=1.23)
        scan.l (r1.25 -> r1.26)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/pllolcode/scan.l.diff?r1=1.25&r2=1.26)
        testFuncs.sql (r1.4 -> r1.5)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/pllolcode/testFuncs.sql.diff?r1=1.4&r2=1.5)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Add a function pg_get_keywords() to let clients find out the set
Next
From: eggyknap@pgfoundry.org (User Eggyknap)
Date:
Subject: pllolcode - pllolcode: Remove some code restricting string lengths.