All,
I've faced problems while adding <subj> into trunk.
For procedure parameters, the syntax is:
COMMENT ON PARAMETER <proc name>.<param name> IS <text>
However, procedures and functions have different namespaces, so there
may be a function and its input parameter with exactly the same names.
Thus this syntax doesn't look suitable for functions. Other options, as
I see them, are underneath.
1) Extend the syntax but preserve backward compatibility via default:
COMMENT ON [{PROCEDURE | FUNCTION}] PARAMETER ...
if the keyword is omitted, procedure parameter is implied. But user
mistakes are possible in this case.
2) Introduce a separate keyword:
COMMENT ON ARGUMENT <func name>.<param name>
This matches the system table name (RDB$FUNCTION_ARGUMENTS) but we
already use the keyword PARAMETER in the syntax RETURNS PARAMETER <n> in
the UDF declaration, so having the same thing named differently doesn't
look nice.
Any other ideas?
Dmitry
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
