Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
pgsql: More trivial dead code removal: in int_to_roman(), checking for
- From: neilc(at)svr1(dot)postgresql(dot)org (Neil Conway)
- To: pgsql-committers(at)postgresql(dot)org
- Subject: pgsql: More trivial dead code removal: in int_to_roman(), checking for
- Date: Tue, 21 Jun 2005 22:43:05 -0300 (ADT)
- Message-id: <20050622014305.B7AAE52886@svr1.postgresql.org> <text/plain>
Log Message:
-----------
More trivial dead code removal: in int_to_roman(), checking for "num == -1"
is redundant after a check has already been made for "num < 0". The "set"
variable can also be removed, as it is now no longer used. Per checking
with Karel, this is the right fix.
Per Coverity static analysis performed by EnterpriseDB.
Modified Files:
--------------
pgsql/src/backend/utils/adt:
formatting.c (r1.88 -> r1.89)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c.diff?r1=1.88&r2=1.89)
- Prev by Date: pgsql: Add a CONTINUE statement to PL/PgSQL, which can be used to begin
- Next by Date: pgsql: Correct some code in pg_restore when reading the header of a tar
- Previous by thread: pgsql: Add a CONTINUE statement to PL/PgSQL, which can be used to begin
- Next by thread: pgsql: Correct some code in pg_restore when reading the header of a tar
- Indexes: