Re: trigger compile problem - Mailing list pgsql-general

From Bruce Momjian
Subject Re: trigger compile problem
Date
Msg-id 200109291815.f8TIFFb21998@candle.pha.pa.us
Whole thread Raw
In response to Re: trigger compile problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> >> I've always wondered why plpgsql is so nitpickingly insistent on finding
> >> a semicolon after the last END.  Would anyone object if I made the
> >> last semi optional?
>
> > C requires the termination.  I assume our languages should too.
>
> I don't think that analogy holds water at all, since plpgsql is not
> C and doesn't emulate C's syntax very closely.  Even if you accept
> the analogy, what we're discussing here is a semicolon after the end
> of a function body, which C does not expect you to write --- so the
> analogy favors omitting it, not requiring it.

Yes, good point.  Also, the end of the string is clearly marking the
_end_, so of like EOF.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: showing also value '0' with aggregate count()
Next
From: Stephan Szabo
Date:
Subject: Re: Dynamic Query problem