At the moment you have a zillion user notes, which is worse? :) Having atleast 9 different notes (str_split before I deleted them all) each with their own version of the function, all of which only worked in a couple of situations is definitly unwanted clutter!
I think putting some information into the migration docs, and the faq is a good suggestion, but I don't think it covers all bases. Aidan "Gabor Hojtsy" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > >>>>I wouldn't have thought that to be an option, but now that you > >>>>mention it - sure, sounds like a great idea. > >>>> > >>>>Would you like me to do it? I'm not sure I have commit access to > >>>>those pages... > >>> > >>>I first would like to hear what other people think about, we are not in > >>>hurry;-) > >> > >>Fine with me. > > > > What's the proposal here? Insert this entity into every > > new PHP feature since PHP 4.2.0... forever? Every new > > function, constant, etc. will refer to this PEAR class? > > Eventually we will have a zillion "tips" for this optional > > information and that will clutter up the manual. > > > > Create a FAQ, put it in the migration docs, maybe even > > somewhere within the tutorial, but everywhere is too > > much information. IMHO of course :) > > The full explanation should not be there on all pages. A small portion > of text could be around on the relevant pages however, linking to that > FAQ entry. > > Goba
