Easy to prevent crash, but the question was how to treat this case?
  We ended up implementing the "global" SPs (i.e. with no associated
  db), which were planned but left unresolved when SPs moved into dbs.
  So now things like "call .p()" work too.

  Althought techically not a but (as it's functioning as designed),
  it was decided that the design should be changed. Some users have
  a problem with dates being '0000-00-00' and the SQL standard specifies
  that the modification date should be the same as the creation date
  at creation.

into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0

into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0

final 0 of the string.

into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0

into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0

Merged the different find_xxxx_table_in_list functions to one + some inline functions

Bug in diff_handlers and diff_cursors made it attempt to pop
the wrong number at jumps sometimes.

into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0

fixed printing of COLLATE operation
(BUG#5155)

into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/mysql-5.0

A lot of the default.c module code was refactored. The patch is needed
for the IM.

Putting initialization into .cc will reduce compiler's abilities
to optimize this constant away.
Defines are not OK as they bloat global namespace.
Looking for a way to declare an efficient named constant in reduced
namespace (i. e. in  a class).
Let's try enums: normally they should be implicitly casted to int.
Let's see if we really have a compiler which won't do that.

into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0

fixed other Item_ref methods where result_field involved