Hmmm, I'm not even sure that "complicates" is even the right word here - counting BEGIN/END block nesting is not the most complex of programming problems. Several years ago I wrote my own SQL statement parser (in Pascal) to automate database upgrades without depending on ISQL being available. My recollection is that it was more complicated adding ISQL set term compatibility (i.e. having to parse a set term statement) than it was to count begin/end block nesting and ignore semi-colons except in the outer block. Anyway, the parser worked regardless of whether set term was used.
Tony Whyman MWA On 15/10/15 16:34, Ann Harrison wrote: >> On Oct 15, 2015, at 9:59 AM, Dimitry Sibiryakov <s...@ibphoenix.com> wrote: >> >> 15.10.2015 15:51, marius adrian popa wrote: >>> In InterBase 7 is changed so procedure and trigger programming language to >>> no longer >>> require the use of SET TERM >> IMHO, this is unnecessary complication of isql's parser. I'd prefer to >> follow KISS concept. > Respectfully disagree. Yes, it complicates isql, but it makes the user's > life easier. One bit of complication in isql, thousands of simpler to > create triggers and procedures. > > Cheers, > > Ann > ------------------------------------------------------------------------------ > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
