On 07/17/12 19:30, Adriano dos Santos Fernandes wrote: > Hi! > > Doesn't it sound clumsy that status string still use this pattern in the > new API? > > As a first glance, I believe that: > 1) Exception class should manage it's memory. When it receives and > status vector, it must alloc. space for strings, copy original ones to > it and manage it. > > 2) IStatus should do the same thing. Always. > 3) Circular buffer must be local to y-valve legacy functions. It should > even be not necessary to export the function in IMaster.
Agreed with all points. Ideally p.1 should go hand by hand with making engine's code throw exceptions instead of returning status in tdbb_status_vector. What about exporting circular buffer support in IMaster - yes, it was temp measure. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
