ID: 25121
Updated by: [EMAIL PROTECTED]
Reported By: obones at meloo dot com
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: Linux
PHP Version: 4.3.2
New Comment:
This have been commited to cvs in june
From: obones at meloo dot com
Operating system: Linux
PHP version: 4.3.2
PHP Bug Type: Documentation problem
Bug description: French XSLT documentation is outdated
Description:
The French documentation for the XLST functions is outdated and as such
innaccurate.
I
thetaphiSun Aug 17 18:15:08 2003 EDT
Modified files:
/phpdoc/en/chapters install.iplanet.xml
Log:
some more infos to ini settings
Index: phpdoc/en/chapters/install.iplanet.xml
diff -u phpdoc/en/chapters/install.iplanet.xml:1.6
phpdoc/en/chapters/install
From: kingjojo75 at hotmail dot com
Operating system: win2k
PHP version: 4.3.2
PHP Bug Type: Documentation problem
Bug description: contridictory statements in install.txt
Description:
the install.txt doc in the windows binaries distros seem to cover several
vers
Hello!
>> >> return 0;
>> >> // 0 aren't variable, it's an expression.
>> >> // should it be return (0); ?
>> >
>> > no, why?
>>
>> If we got the rules strictly, 0 is an expression, not a
>> variable. But that's a really basic expression :)
>>
>> What about arrays?
>
> I agree with Derick. What is
On Sun, 2003-08-17 at 07:39, Heilig (Cece) Szabolcs wrote:
> Hello!
>
> >> return 0;
> >> // 0 aren't variable, it's an expression.
> >> // should it be return (0); ?
> >
> > no, why?
>
> If we got the rules strictly, 0 is an expression, not a
> variable. But that's a really basic expression :)
>
derick Sun Aug 17 15:09:25 2003 EDT
Modified files:
/phpdoc/en/faq html.xml
Log:
- Pretty up examples
Index: phpdoc/en/faq/html.xml
diff -u phpdoc/en/faq/html.xml:1.21 phpdoc/en/faq/html.xml:1.22
--- phpdoc/en/faq/html.xml:1.21 Tue Apr 8 23:22:19 2003
Derick Rethans wrote:
On Thu, 14 Aug 2003, Mehdi Achour wrote:
> What about french documentation ? =D
This was so unexpected *sigh*
Derick
A greek phpdoc-el build would be nice and useful.. If its too much of a
headache, I can have it build.
It's been months now that we only have a
Here's what I wanted to talk about. I want to ask for something btw..
who will take the decision of changing the system or not ?
any clue ?
There is no single person. The magic word community decision comes to
mind :) Which means if noone objects, and those providing comments,
agree, then it is
Mehdi Achour wrote:
Hi !
[ .. ]
Here's what I wanted to talk about. I want to ask for something btw..
who will take the decision of changing the system or not ?
any clue ?
didou
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Hello!
>> Pear documentation talking about only control statements. Array
>> is closer than internal functions than control structures, but it's
>> not a real function, only a language construct.
>
> It is not closer to a function at all... that's nonsense.
array() returns an array, based on mixe
On Sun, 17 Aug 2003, Heilig (Cece) Szabolcs wrote:
> Pear documentation talking about only control statements. Array
> is closer than internal functions than control structures, but it's
> not a real function, only a language construct.
It is not closer to a function at all... that's nonsense.
D
> language construct. Array doesn't controls the flaw of the
sorry, i meant flow ;-)
Cece
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.ph
>> But what about arrays? Can we discuss Pear guys about that?
>
> I don't mind that much for arrays, but it *is* a language construct, and
> from what I read from the CS that means that there should be a space
> there.
"Control statements should have one space between the control keyword and
open
On Sun, 17 Aug 2003, Heilig (Cece) Szabolcs wrote:
>
> > You shouldn't use () with echo anyway, it can do things you won't
> > expect. array and return are control structures too, so I don't see why
> > they should be different. (array is not that obvious, but return is
> > definitely a control s
On Sun, 17 Aug 2003, Heilig (Cece) Szabolcs wrote:
> Hello!
>
> >> return 0;
> >> // 0 aren't variable, it's an expression.
> >> // should it be return (0); ?
> >
> > no, why?
>
> If we got the rules strictly, 0 is an expression, not a
> variable. But that's a really basic expression :)
Sure, 0
Hello!
>> return 0;
>> // 0 aren't variable, it's an expression.
>> // should it be return (0); ?
>
> no, why?
If we got the rules strictly, 0 is an expression, not a
variable. But that's a really basic expression :)
What about arrays?
--
===
On Sun, 17 Aug 2003, Heilig (Cece) Szabolcs wrote:
> Hello!
>
> Here are some appereances of return in examples:
>
> return 0;
> // 0 aren't variable, it's an expression.
> // should it be return (0); ?
no, why?
>
> return ($a < $b) ? -1 : 1;
> // expression, i think return (($a < $b) ? -1 :
Hello!
Here are some appereances of return in examples:
return 0;
// 0 aren't variable, it's an expression.
// should it be return (0); ?
return ($a < $b) ? -1 : 1;
// expression, i think return (($a < $b) ? -1 : 1); is the
// right choice
It's ok?
Cece
--
PHP Documentation Mailing List (h
There could be an optional text box...
in case you want to give it a reason for deleting etc..
Rememeber that most of the moderation are done wia the mail client.
Having a text box will mean openeing a new broser page each time. is
that needed ?
Not needed. But would be a possible option.
Goba
wrong : the user is posting a poorly written code, is saying
something wrong, is answering to
someone else
I think separating ugly from misleading is not a bad idea.
ugly_useless: the user is posting a poorly written code, is answering to
someone else's question
> wrong : the user is posting a poorly written code, is saying
> something wrong, is answering to
> someone else
I think separating ugly from misleading is not a bad idea.
ugly_useless: the user is posting a poorly written code, is answering to
someone else's qu
Allowee wrote:
On Sunday 17 August 2003 15:18, Mehdi Achour wrote:
Reasons: i think, sometimes is good to specify text on reason,
not just select from a list.
IMHO, we can't ask a moderator to type a reason for every note he
delete/reject.
There could be an optional text box...
in case you wan
Reasons: i think, sometimes is good to specify text on reason,
not just select from a list.
IMHO, we can't ask a moderator to type a reason for every note he
delete/reject.
But we can provide some quickfixes, and still a possibilty to provide
any comment instead of a quickfix.
Goba
--
PHP Docum
On Sunday 17 August 2003 15:18, Mehdi Achour wrote:
> > Reasons: i think, sometimes is good to specify text on reason,
> > not just select from a list.
>
> IMHO, we can't ask a moderator to type a reason for every note he
> delete/reject.
There could be an optional text box...
in case you want to
Heilig Szabolcs wrote:
here's IMHO what we'll need :
bad_mail: the note should be rejected, but the provided mail
is buggy, no need to give more
work to the server.
+bad_thinking: the note based on misunderstood, mistake, etc...
isn't this covered by "wrong" ?
Reasons:
>here's IMHO what we'll need :
>
> bad_mail: the note should be rejected, but the provided mail
> is buggy, no need to give more
> work to the server.
+bad_thinking: the note based on misunderstood, mistake, etc...
Reasons: i think, sometimes is good to specify text on
On Sun, 2003-08-17 at 15:13, Heilig (Cece) Szabolcs wrote:
>
> > You shouldn't use () with echo anyway, it can do things you won't
> > expect. array and return are control structures too, so I don't see why
> > they should be different. (array is not that obvious, but return is
> > definitely a co
didou Sun Aug 17 09:17:22 2003 EDT
Modified files:
/phpdoc/en/reference/ftp/functions ftp-mdtm.xml
Log:
missing title and WS
Index: phpdoc/en/reference/ftp/functions/ftp-mdtm.xml
diff -u phpdoc/en/reference/ftp/functions/ftp-mdtm.xml:1.4
phpdoc/en/reference/
didou Sun Aug 17 09:14:23 2003 EDT
Modified files:
/phpdoc/en/reference/ftp/functions ftp-exec.xml ftp-fput.xml
ftp-get.xml ftp-mdtm.xml
ftp-rmdir.xml ftp-size.xml
Log:
adding exam
> You shouldn't use () with echo anyway, it can do things you won't
> expect. array and return are control structures too, so I don't see why
> they should be different. (array is not that obvious, but return is
> definitely a control structure (it controls the end of a
> function/include file)).
Hi !
Before my departure on holiday, I would like to come back to the subject
of the users notes. The actual system seffers many problems, leading to
a certain "anarchy".
There's a need to change it, and to modify a bit the policy of his use.
4 points to deal with :
1) Who is allowed to manage
On Sun, 17 Aug 2003, Gabor Hojtsy wrote:
> >>>actually, array and return are language constructs, so they should have
> >>>the space, like:
> >>
> >>>array ('foo');
> >>
> >>That elements are lang.contructs, but looks like as functions.
> >>So, i checked PEAR codes. All PEAR codes (including class
actually, array and return are language constructs, so they should have
the space, like:
array ('foo');
That elements are lang.contructs, but looks like as functions.
So, i checked PEAR codes. All PEAR codes (including class Pear
in PEAR.php) handles array() as functions, without spaces before
ope
On Sun, 17 Aug 2003, Heilig (Cece) Szabolcs wrote:
> > actually, array and return are language constructs, so they should have
> > the space, like:
>
> > array ('foo');
>
> That elements are lang.contructs, but looks like as functions.
> So, i checked PEAR codes. All PEAR codes (including class
On Sun, 17 Aug 2003, Heilig (Cece) Szabolcs wrote:
> Log:
> applying PEAR coding standards on examples
actually, array and return are language constructs, so they should have
the space, like:
array ('foo');
and
return ($foo %2);
...
It's better to ask first before applying such a large
ceceSun Aug 17 08:21:04 2003 EDT
Modified files:
/phpdoc/en/reference/array/functionsarray-combine.xml
array-count-values.xml
array-diff-assoc.xml
ceceSun Aug 17 08:16:16 2003 EDT
Modified files:
/phpdoc/en/reference/array/functionsreset.xml
Log:
sorry, did not checked before committed :(
Index: phpdoc/en/reference/array/functions/reset.xml
diff -u phpdoc/en/reference/array/functions/reset.xml:
ceceSun Aug 17 08:12:48 2003 EDT
Modified files:
/phpdoc/en/reference/array/functionsreset.xml
Log:
added example
Index: phpdoc/en/reference/array/functions/reset.xml
diff -u phpdoc/en/reference/array/functions/reset.xml:1.5
phpdoc/en/reference/arra
>
> Can't we ask each translation team to provide its language differents
> formats of documentation to [EMAIL PROTECTED] ? I think it will get rid of
> the load. The system team will only have to test them and then put them
> online. Opinions ?
+1
moshe
--
PHP Documentation Mailing List (
Hi Curt!
I'm a involved on the php-general list helping people
out. After repeated questions being asked on that list kind of
force me to join this list to see what has/is been going on with
the documentation. Plus I would be able to help with making the
documentation clearer.
Welcome :)
One of t
didou Sun Aug 17 05:43:19 2003 EDT
Modified files:
/phpdoc/en/appendices migration.xml
Log:
correcting closing mark
Index: phpdoc/en/appendices/migration.xml
diff -u phpdoc/en/appendices/migration.xml:1.23 phpdoc/en/appendices/migration.xml:1.24
--- phpd
42 matches
Mail list logo
