pllolcode - pllolcode: Improve string handling in lex scanner by

From: eggyknap(at)pgfoundry(dot)org (User Eggyknap)
To: pgsql-committers(at)postgresql(dot)org
Subject: pllolcode - pllolcode: Improve string handling in lex scanner by
Date: 2008-07-04 01:04:53
Message-ID: 20080704010453.82CCA17AE71D@pgfoundry.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message User Eggyknap 2008-07-04 01:12:41 pllolcode - pllolcode: Remove some code restricting string lengths.
Previous Message Tom Lane 2008-07-03 20:58:47 pgsql: Add a function pg_get_keywords() to let clients find out the set