(including
removing the old chapters/instal./.xml)?
There's no hurry to remove the old files;-)
The hurry is just because 'make test' will fail if you don't delete those
files (because of ID colisions)
Ehem, you don't need to remove files, you just need to remove the
references to them. But only l
I thought about twice and I wonder why it is preferable to use PHPRC
instead
just copy php-(sapiname).ini to SYSTEMROOT?
Using PHPRC is indeed nice but seems to be a superfluous hurdle for
newbies.
We do not talk about 'copy dlls' just one/two ini-files to SYSTEMROOT.
Nothing
wrong with that, IMHO.
Hello,
Do we have an IRC channel where everyone gathers? I see 10 or so people in
#phpdoc in freenode, no names I recognise.
What would you guys say moving to efnet #php.doc? It would be nice to have a
place to discuss ... stuff.
What do you think?
Kind Regards,
Aidan
> Uhm, copying the php.ini file to the windows folder isn't that bad. (as it
> isn't updated)
Yes it is :)
Don't do it :)
Ini files in the windows folder have been a strongly deprecated
practice since win95 and the registry emerged.
php-{sapi}.ini is the best practice, and keep it out of a global
> I thought about twice and I wonder why it is preferable to use PHPRC
instead
> just copy php-(sapiname).ini to SYSTEMROOT?
>
> Using PHPRC is indeed nice but seems to be a superfluous hurdle for
newbies.
> We do not talk about 'copy dlls' just one/two ini-files to SYSTEMROOT.
Nothing
> wrong with
> Nice done;-)
Thanks!
> I only had a brief look, but following comes to my mind:
> Manual Installation Steps:
> I would like to advice people to use php-(sapiname).ini or at least
mention
> this somewhere.
> I like to suggest that setup of a valid php.ini file is moved to the
server
> specific i
nlopess Mon Aug 2 17:33:03 2004 EDT
Modified files:
/phpdoc/en/install/windows apache1.xml apache2.xml index.xml
manual.xml
/phpdoc/en/faq installation.xml
Log:
re-write of the windows install section. still need some re
On Monday 02 August 2004 12:11, Gabor Hojtsy wrote:
> > http://testes.aborla.net/phpdoc/install.windows.html
> > http://testes.aborla.net/phpdoc/faq.installation.html#faq.installation.ad
> >dtopath
> >
> > diff: http://testes.aborla.net/win.install.diff
>
> Just a few notes :)
>
[..]
> 8. It is sti
On Monday 02 August 2004 17:35, Derick Rethans wrote:
> On Mon, 2 Aug 2004, Derick Rethans wrote:
> > > User should know that some parameter can be changed by function as it
> > > is passed by reference.
> >
> > 100% agreed on that.
Ok, Ok, convinced ;-) thinking about after enough sleep ;-))
> 3. Planning for the future, I have also added an internal
> link on the ActiveScript engine stuff, so we can document
> how can it be registered as a Windows Scripting Host
> provider, and used for scripting. That is a short and easy
> to write part and should be included in the W
ceceMon Aug 2 16:06:30 2004 EDT
Modified files:
/phpdoc/en/reference/url/functions base64-encode.xml
base64-decode.xml
Log:
ws fix
http://cvs.php.net/diff.php/phpdoc/en/reference/url/functions/base64-encode.xml?r1=1
Curt Zirzow wrote:
* Thus wrote Derick Rethans:
On Mon, 2 Aug 2004, Derick Rethans wrote:
User should know that some parameter can be changed by function as it is
passed by reference.
100% agreed on that.
That said, I'm not sure if adding & before the variable name is a
good idea though I can't se
On Sunday 01 August 2004 17:54, Gabor Hojtsy wrote:
> >>And now? Advice Apache 1 users to copy php.ini to C:\windows (or C:\winnt
> >>for win NT/2k)?
> >
> > Advice them to name the file php-apache.ini ;-)
> >
> > Could not recall if the option for naming the inis like the used sapi is
> > document
On Monday 02 August 2004 12:14, Gabor Hojtsy wrote:
> > I only had a brief look, but following comes to my mind:
> > Manual Installation Steps:
> > I would like to advice people to use php-(sapiname).ini or at least
> > mention this somewhere.
>
> I would second that the SAPI specific ini file name
* Thus wrote Derick Rethans:
> On Mon, 2 Aug 2004, Derick Rethans wrote:
>
> > > User should know that some parameter can be changed by function as it is
> > > passed by reference.
> >
> > 100% agreed on that.
>
> That said, I'm not sure if adding & before the variable name is a
> good idea thoug
Hi Nuno,
You know, I went and searched the lists immediately *after* I posted, and
saw what was going on :( Sorry about not doing that sooner, but thanks for
taking care of this; I really appreciate it!
Cheers,
--
Justin M
Technical Support
VeriSign Payment Services
[EMAIL PROTECTED]
888-883-97
On Mon, 2 Aug 2004, Derick Rethans wrote:
> > User should know that some parameter can be changed by function as it is
> > passed by reference.
>
> 100% agreed on that.
That said, I'm not sure if adding & before the variable name is a
good idea though I can't see any other way of doing this.
Der
On Mon, 2 Aug 2004, Jakub Vrana wrote:
> > On Monday 02 August 2004 01:33, M. Sokolewicz wrote:
> >> I think we should convert all to the 2nd type, it's just clearer...!
> >> any comments?:)
>
> I agree.
>
> Friedhelm Betz wrote:
> > No, because the function definitions make sure which arguments a
Gabor Hojtsy wrote:
I think we should convert all to the 2nd type, it's just clearer...!
any comments?:)
No, because the function definitions make sure which arguments are
passed by reference. There is no need to even know this sort of
information.
Users need to know where they need to pass a v
ID: 29018
Comment by: josh at vodafone dot de
Reported By: none at space dot com
Status: Feedback
Bug Type: Documentation problem
Operating System: any
PHP Version: 4.3.6
New Comment:
Workarounds? How elegant! :P
You got to be kidding, ri
i didn't followed the last livedocs patchs but the last time i test it,
after the rtl stuff was commited, its just worked fine.
Great, so then I can just pull off my unread mails from that TODO list :)
Goba
i didn't followed the last livedocs patchs but the last time i test it,
after the rtl stuff was commited, its just worked fine.
Moshe.
"Gabor Hojtsy" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> What is the status of RTL support in livedocs?
>
> Goba
>
> moshe doron írta:
> > you
What is the status of RTL support in livedocs?
Goba
moshe doron írta:
you correction is mistake. RTL and CHARSET are defines not vars at all.
--/moshe
"Nuno Lopes" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Moshe, as I've already told you, your patch had a little bug with GLOBALS.
Gabor Hojtsy wrote:
>> Nobody answered :-(. In the mean-time, I wrote a script with this
>> purpose. Should I add it to CVS?
> Yes, please :)
Committed.
Jakub Vrana
vrana Mon Aug 2 07:25:09 2004 EDT
Added files:
/phpdoc/scripts xml-check.php
Log:
Check syntax of single manual page
http://cvs.php.net/co.php/phpdoc/scripts/xml-check.php?r=1.1&p=1
Index: phpdoc/scripts/xml-check.php
+++ phpdoc/scripts/xml-check.php
On Fri, 30 Jul 2004, Philip Olson wrote:
> Here are some questions/concerns about having all PECL docs
> inside of phpdoc:
>
> Builds:
> Will all or just bundled PECL docs be in phpdoc manual builds?
All.
> Meaning, will a separate PECL manual ever exist?
No
> As PECL grows
> the manual will g
vrana Mon Aug 2 06:54:00 2004 EDT
Modified files:
/phpdoc/en/language operators.xml
Log:
Associativity, precedence, remove print\n# internals@ didn't object
http://cvs.php.net/diff.php/phpdoc/en/language/operators.xml?r1=1.76&r2=1.77&ty=u
Index: phpdoc/en/lan
This is kind of FUD if you don't provide details, it just sparks fear
and does not help anything.
Goba
There are several bug reports regarding security of sessions on
multi-user environments, there is mail from Peter Brodersen about this
to internals@ (http://news.php.net/php.internals/11549), th
Downloads should be smaller somehow like only include bundled
extensions.
What about building two manual versions - one with PECL and one without?
IMHO it's not necessary nowadays as there are only a few PECL extensions
documented but will be more important when the majority of 314
extensions (inst
Version info:
Is this issue solved, will this go into the manual docs?
Ref: http://marc.theaimsgroup.com/?l=phpdoc&m=107574257608183
I will try to modify versioning script to mark PECL functions. It will
mark them without version number in the first step. Then we can improve
the script to mark the
I only had a brief look, but following comes to my mind:
Manual Installation Steps:
I would like to advice people to use php-(sapiname).ini or at least mention
this somewhere.
I would second that the SAPI specific ini file names need more promotion!
I like to suggest that setup of a valid php.ini
b.): Use PHPRC, can be mor than one location, e.g.: c:\; d:\; c:\php etc.
If PHPRC can be more than one location, it would be very nice to mention
somewhere!
Goba
http://testes.aborla.net/phpdoc/install.windows.html
http://testes.aborla.net/phpdoc/faq.installation.html#faq.installation.addtopath
diff: http://testes.aborla.net/win.install.diff
Just a few notes :)
1. > either manually or by using the installer installer.
Philip Olson wrote:
> Version info:
> Is this issue solved, will this go into the manual docs?
> Ref: http://marc.theaimsgroup.com/?l=phpdoc&m=107574257608183
I will try to modify versioning script to mark PECL functions. It will
mark them without version number in the first step. Then we can im
There are several bug reports regarding security of sessions on
multi-user environments, there is mail from Peter Brodersen about this
to internals@ (http://news.php.net/php.internals/11549), there is mail
from me with brief summary to security@ and nothing happens.
Don't you mind if I add this wa
Philip Olson wrote:
> Downloads should be smaller somehow like only include bundled
> extensions.
What about building two manual versions - one with PECL and one without?
IMHO it's not necessary nowadays as there are only a few PECL extensions
documented but will be more important when the majorit
vrana Mon Aug 2 05:32:15 2004 EDT
Modified files:
/phpdoc/en/reference/info/functions get-defined-constants.xml
/phpdoc/en/reference/funchand/functions get-defined-functions.xml
/phpdoc/en/reference/var/functions get-defined-vars.xml
Log:
See also
I think we should convert all to the 2nd type, it's just clearer...!
any comments?:)
No, because the function definitions make sure which arguments are passed by
reference. There is no need to even know this sort of information.
Users need to know where they need to pass a variable (as opposed to
tularisSun Aug 1 19:20:42 2004 EDT
Modified files:
/phpdoc/en/reference/array/functionsnatsort.xml Log:
added the & to the parameter to make it clear(er) that this
parameter is passed by reference
I think this should be done in more places... right now it's in
Friedhelm Betz wrote:
> a.): As you mentioned, copy to SYSTEMROOT
> b.): Use PHPRC, can be mor than one location, e.g.: c:\; d:\; c:\php etc.
> c.): copy ini file to the same folder apache.exe lives in (this also works for
> lbmysql.dll and libmysqli.dll)
There's also registry entry HKLM\Software\
> On Monday 02 August 2004 01:33, M. Sokolewicz wrote:
>> I think we should convert all to the 2nd type, it's just clearer...!
>> any comments?:)
I agree.
Friedhelm Betz wrote:
> No, because the function definitions make sure which arguments are passed by
> reference. There is no need to even kno
41 matches
Mail list logo