On 02/07/15 16:43, Dmitry Yemanov wrote: > 07.02.2015 13:27, Alex Peshkoff wrote: >> I.e. if we decide to go this way we should do this with all catch blocks >> which is a change not differing much in volume of changes from changing >> tdbb_status_vector to something capable to store unlimited length vectors. > True. But I don't suggest to do that in v3, except the looper (two catch > blocks and exeState). And v4 deserves a better (long-term) solution, > then the looper can be adjusted to the new rules. > >
If it's so local I think we can live with it in v3. But we have one more related problem - after adding line/column info errors stopped to fit into status array. I suppose this should be also fixed in v3. May be extending status vector internally? ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
