Actually, I think it might be better to completely remove all references to
aliases. People don't need to use them and they are only there to keep old
code from breaking. The less people know about them, the better really.
If we still need some sort of compatibility list, we could always create an
alias/compatibility appendix and list all alias functions there. That way,
they would at least be accessible to people who are reading or converting
very old code.
Daniel
----- Original Message -----
From: "Damien Seguy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 2:39 AM
Subject: [PHP-DOC] missing aliases functions
> Hi,
>
> This might a question for those of you who are on this list
> since a year or so...
>
> According to Zend's site (http://www.zend.com/phpfunc/nodoku_alias.php),
> there is a bunch of undocumented functions which are only aliases.
>
> Docs says that, for instance, mysql() is still available for downward
> compatibility, but there is no entry for mysql() function.
>
> Is this done on any purpose?
> I suggest adding those functions, in order to give entry on the manual,
and
> explicitely write those functions are obsolets.
>
> If this sounds fine to you, I'll do it.
>
> Best regards,
> Damien Seguy.
>
> Here is a list of function I'm talking about.
>
> mysql -> mysql_db_query
> mysql_createdb -> mysql_create_db
> mysql_dbname -> mysql_result
> mysql_dropdb -> mysql_drop_db
> mysql_fieldflags -> mysql_field_flags
> mysql_fieldlen -> mysql_field_len
> mysql_fieldname -> mysql_field_name
> mysql_fieldtable -> mysql_field_table
> mysql_fieldtype -> mysql_field_type
> mysql_freeresult -> mysql_free_result
> mysql_listdbs -> mysql_list_dbs
> mysql_listfields -> mysql_list_fields
> mysql_listtables -> mysql_list_tables
> mysql_numfields -> mysql_num_fields
> mysql_numrows -> mysql_num_rows
> mysql_selectdb -> mysql_select_db
> pg_clientencoding -> pg_client_encoding
> pg_setclientencoding -> pg_set_client_encoding
> magic_quotes_runtime -> set_magic_quotes_runtime
>
>
>
