26.01.2014 00:56, Helen Borrie wrote: >> However current situation should be reflected in Release Notes. > > From a design perspective, my simple-minded view is that homonymity of the > kind that leads to conflicts within the scope of the current_schema should be > avoided. You seem to be saying that the Release Notes should document your > "sloppy design" edge cases...or have I totally misunderstood?
AFAIU, his point is to document that it's currently impossible to call a global routine with the same name as the packaged routine (if called from inside that package). Dmitry ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
