Re: [Firebird-devel] Comments for function parameters

2011-07-14 Thread Paul Vinkenoog
Dmitry wrote: > > Extend the syntax but preserve backward compatibility via default: > > > > COMMENT ON [{PROCEDURE | FUNCTION}] PARAMETER ... > > but if the object type specifier is omitted, then the engine tries to be > smart and determine whether it's a procedure or a function at runtime > (by

Re: [Firebird-devel] Comments for function parameters

2011-07-14 Thread Dimitry Sibiryakov
14.07.2011 18:33, Dmitry Yemanov wrote: > I'm now convincing myself to the third option: For me this option looks better than previous two. -- SY, SD. -- AppSumo Presents a FREE Video for the SourceForge Community

Re: [Firebird-devel] Comments for function parameters

2011-07-14 Thread Dmitry Yemanov
I'm now convincing myself to the third option: > Extend the syntax but preserve backward compatibility via default: > > COMMENT ON [{PROCEDURE | FUNCTION}] PARAMETER ... but if the object type specifier is omitted, then the engine tries to be smart and determine whether it's a procedure or a fun

[Firebird-devel] Comments for function parameters

2011-07-14 Thread Dmitry Yemanov
All, I've faced problems while adding into trunk. For procedure parameters, the syntax is: COMMENT ON PARAMETER . IS 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 sui