On Tue, Nov 04, 2008 at 05:47:04PM +0100, Patryk Zawadzki wrote: > On Tue, Nov 4, 2008 at 5:39 PM, Tomasz Pala <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 04, 2008 at 10:04:40 +0100, Patryk Zawadzki wrote: [...] > >> patch -p0 -l < foo.patch > >> > >> to break the code instead of failing. > > Oh, breaking the code by dumb patching is always a case. The point is: > > 'patch -l' DOESN'T break anything as you were saying. > > Breaking the code in this way and for dynamically compiled languages > means we'll find the error two weeks after building a package. > > It DOES break the code by making it invalid (if this happened in the > middle of the file you'd get a nice syntax error at run-time due to > broken indentation or just buggy behavior depending on the place in > the code block) and giving no error at patch-time. Ignoring whitespace > in Python is like ignoring dots in brainfuck or ignoring brace in C.
What about ignoring whitespaces in patches to code in Whitespace language? ;> -- Jakub Bogusz http://qboosh.pl/ _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
