At 15:25 26-8-2002, [EMAIL PROTECTED] wrote:
>On Mon, 26 Aug 2002, Marcus Börger wrote:
>
> > But then we would have different outputs on different systems.
> > So i am against using diff when installed.
>
>Why not always use our own code? That way it's the same on every
>platform.
Use our own c
On Mon, 26 Aug 2002, Marcus Börger wrote:
> But then we would have different outputs on different systems.
> So i am against using diff when installed.
Why not always use our own code? That way it's the same on every
platform.
Derick
> At 14:59 22.08.2002, Sander Roobol wrote:
> >It's a good
But then we would have different outputs on different systems.
So i am against using diff when installed.
marcus
At 14:59 22.08.2002, Sander Roobol wrote:
>It's a good idea, but I'd rather see an unified diff with some context.
>Maybe use diff when it's available, and fall back on this code when
It's a good idea, but I'd rather see an unified diff with some context.
Maybe use diff when it's available, and fall back on this code when
it's not.
Sander
On Thu, Aug 22, 2002 at 02:46:57AM +0200, Marcus Boerger wrote:
> The following patch produces *.diff files similar to
> diff command. The
The following patch produces *.diff files similar to
diff command. These would allow for easier checks in faild tests
when test combines multiple function checks in one test file
or the test uses var_dump for output.
For example i changed precision to 13 in array test 003.phpt
The tests now produ
