I have noticed bit weird behavior of symlink() & link() where given an
invalid input like NULL, true, empty string ('') works fine on SuSE 9 64bit
& Fedora core 3 64-bit. Its hard to make things always portable but things
of this sort can be avoided if we tried to do strict type checking of the
in
On 6/28/07, Zoe Slattery <[EMAIL PROTECTED]> wrote:
Derick Rethans wrote:
> On Thu, 28 Jun 2007, Zoe Slattery wrote:
>
>
>> Hi
>>
>> I think there are two user scenarios to consider:
>>(a) User works only on platform X and extpects the PHP function to return
>> exactly what he would see from
Derick Rethans wrote:
On Thu, 28 Jun 2007, Zoe Slattery wrote:
Hi
I think there are two user scenarios to consider:
(a) User works only on platform X and extpects the PHP function to return
exactly what he would see from (say) the equivalent C function
(b) User works on multiple platf
On Thu, 28 Jun 2007, Zoe Slattery wrote:
> Hi
>
> I think there are two user scenarios to consider:
>(a) User works only on platform X and extpects the PHP function to return
> exactly what he would see from (say) the equivalent C function
>(b) User works on multiple platforms and wants h
Hi
I think there are two user scenarios to consider:
(a) User works only on platform X and extpects the PHP function to
return exactly what he would see from (say) the equivalent C function
(b) User works on multiple platforms and wants his PHP app to behave
exactly the same way across al
On 27.06.2007 18:26, Zoe Slattery wrote:
Hi Tony
The filesystem tests are diffficult and require some compromises - it
isn't easy to work out exactly where.
Well, that's what we're trying to solve here, right? =)
If we change tests so that they pass on as many OS as possible, for
example b
Hi Tony
The filesystem tests are diffficult and require some compromises - it
isn't easy to work out exactly where.
If we change tests so that they pass on as many OS as possible, for
example by changing %d to %i, we'll be relaxing some of the strictness
of the test. If we do this the funct
