On 2004/04/03, at 1:55, Ilia Alshanetsky wrote:
On April 2, 2004 11:42 am, Clemens Gutweiler wrote:
Uh, huh? The behaviour in 4.3.5 is the same as always. Nothing has
changed here. It was simple user error in that report.
Fixed.
Since when did people stop believing what I say? Anyway, I'm fine
On April 2, 2004 11:42 am, Clemens Gutweiler wrote:
> > Uh, huh? The behaviour in 4.3.5 is the same as always. Nothing has
> > changed here. It was simple user error in that report.
Fixed.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.
Hi Rasmus,
> From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]
> Uh, huh? The behaviour in 4.3.5 is the same as always. Nothing has
> changed here. It was simple user error in that report.
Result of Ilia's test-script with PHP 4.3.3:
array(2) {
[0]=>
string(3) "one"
[1]=>
string(4) "va
Uh, huh? The behaviour in 4.3.5 is the same as always. Nothing has
changed here. It was simple user error in that report.
-Rasmus
On Fri, 2 Apr 2004, Moriyoshi Koizumi wrote:
> Hi,
>
> As this bug was already marked as a documentation problem and
> handled by Rasmus, but I don't think this is
I've just tried the script an both PHP 4.3.6, 4.2.3 and 5.0 return the same
results.
Result:
array(2) {
[0]=>
string(3) "one"
[1]=>
string(4) "val1"
}
array(2) {
[0]=>
string(3) "two"
[1]=>
string(4) "val2"
}
array(1) {
[0]=>
string(0) ""
}
array(2) {
[0]=>
string(5) "t
that kind, because versions prior to 4.3.5 returns an array
that contains a null string element and the script supplied
by the user on bug #27730 had worked flawlessly.
Here I mean: because in versions prior to 4.3.5 fgetcsv()
returns an array that contains a null string element for an
empty line..
