Hi Daniel
On 2/12/07, Daniel Convissor <[EMAIL PROTECTED]> wrote:
Hi Folks:
I was looking through the manual for info on upgrading to 5.2 and found
nothing. With some good Googling I found
http://www.php.net/UPDATE_5_2.txt.
You didn't read the release announcement, did you? :)
Of course, it's best to have stuff in the manual, so I took the text from
UPDATE_5_2.txt and formatted it like en/appendices/migrating5.xml. I'm
nearly done and will open a bug in the near future with a link to the
uploaded file.
You will be loved for it, it has been on our todo list since the
release of 5.2.0.
(_NOW_ :)) I noticed that the documentation build system automatically
transforms <function>function_name</funciton> into the function with a
link to the function's documentation. Very nice! From all the work on
the PEAR docs, I'm used to having to manually put in the <link>'s around
the <function>'s so had been putting them.
Question: What are the rules with how the link's are added. Will the
system automatically figure everything out? Even things like this?
<function>XMLReader::open</function>
That depends on the ID of the function/method, this particular case wont work.
In general method IDs are in the form of: function.classname-method
The ID of XMLReader::open is function.xmlreader-open
ergo => <function>xmlreader-open</function> would work.
Note that the IDs (and therefor <function />) are case-insensitive,
but please be consistent with what is used in docs for that
method/function.
-Hannes
I don't want to undo all of the effort of manually putting in all of the
<link>'s so far only to find out they're needed in some cases.
Please cc me, I'm not on [EMAIL PROTECTED]
Thanks,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
