Bug #31900 Wrong confusing comment in mysql_com.h header file

Description:
In mysql_com.h, at line 397, this struct is defined:

typedef struct st_udf_init
{
  my_bool maybe_null;			/* 1 if function can return NULL */
  unsigned int decimals;		/* for real functions */
  unsigned long max_length;		/* For string functions */
  char	  *ptr;				/* free pointer for function data */
  /* 0 if result is independent of arguments */
  my_bool const_item;
  void *extension;
} UDF_INIT;

The comment for my_bool const_item seems wrong or is else confusing. It would make more sense that 0 means the function does not return a constant.

The documentation at http://dev.mysql.com/doc/refman/5.1/en/udf-calling.html does seem to describe the expected behaviour, so at least, these two are in contradiction

How to repeat:
mysql_com.h, at line 397; 
http://dev.mysql.com/doc/refman/5.1/en/udf-calling.html

Suggested fix:
Correct comment in source. Alternatively, fix documentation

Thank you for a bug report. Verified just as described.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/38430

ChangeSet@1.2698, 2007-11-25 00:57:34+04:00, holyfoot@mysql.com +1 -0
  Bug #31900 Wrong confusing comment in mysql_com.h header file.
  
  comment fixed as we truly need const_item to be 1 to mark
  constant function

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/38503

ChangeSet@1.2698, 2007-11-26 16:25:18+04:00, holyfoot@mysql.com +1 -0
  Bug #31900 Wrong confusing comment in mysql_com.h header file.
  
  comment fixed as we truly need const_item to be 1 to mark
  constant function

Pushed into 4.1.24

Pushed into 5.0.54

Pushed into 5.1.23-rc

Pushed into 6.0.5-alpha

No changelog entry needed.