Re: developers manual and users manual

> Hmm, ambiguous? Maybe I am missing something and > "Developer" == "User" in a non-English and non-Spanish > European/Slavic/Oriental language? The problem is that a major part of our user base think that they develop IN PHP, so they are PHP developers... Just search for "java developer" or "c developer" in google, and you'll find sites for guys developing IN Java/C and not developing Java/C itself. So this is why "Developers Manual" may not be appropriate... > In any case, if you really want to be clear on what > you mean, we should have the following: > > 1) Language Reference > > 2) Functions Reference (aka Library Reference) > > 3) PHP Internals and Extension Development > > i.e. a model like the one for Python's documentation > which, in case you missed it in my previous msg, is at > the URL: > > http://www.python.org/doc/ > > Of course, this will make thing a little more > complicated initially, but will be easier from the > manual building/maintainance point of view. The > "Function Reference" changes more often than the > others, so the manual generation schedule can be > changed to reflect that. I can see your point here, but this needs to be discussed widely, so we do not make big changes without knowing that we are doin the right thing (TM). Goba