Re: splitting plpython into smaller parts
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Jan Urbański <wulczer@wulczer.org>, Greg Smith <greg@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-12-15T15:16:29Z
Lists: pgsql-hackers
Excerpts from Peter Eisentraut's message of jue dic 15 12:00:13 -0300 2011: > How to people feel about naming the files (as proposed) > > ! OBJS = plpython.o plpython_io.o plpython_procedure.o plpython_exec.o \ > ! plpython_plpy.o plpython_spi.o plpython_result.o plpython_cursor.o \ > ! plpython_plan.o plpython_subtransaction.o plpython_functions.o \ > ! plpython_elog.o > > vs. say > > ! OBJS = main.o io.o procedure.o exec.o plpy.o spi.o result.o cursor.o \ > ! plan.o subtransaction.o functions.o elog.o > > ? I find the extra prefix unnecessary and ugly; if we had to had a prefix, I'd choose a shorter one (maybe "py" instead of "plpython_"). -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support