bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: feature request: file_not_found_handle()


From: Andreas Gregor Frank
Subject: Re: feature request: file_not_found_handle()
Date: Wed, 21 Aug 2013 20:39:53 +0200

Hello Greg,

this is a feature request for no_such_file_or_directory_
handle(). I do not want to talk about missing quotes in anyone's code
example!
And the question if it makes sense to implement a
command_not_found_handle() in this or that way has nothing to do with this
request, too.
How someone uses a bash feature in his scripts is not the problem of this
mailing list i hope.

Andreas
.



2013/8/21 Greg Wooledge <address@hidden>

> On Wed, Aug 21, 2013 at 02:22:24AM -0800, Ken Irving wrote:
> >     $ cat $(ambler.method dispatch)
> >     #!/bin/bash
> >     method=$1 && shift
> >     test -n "$method" || exit
> >     for s in $(ls|shuf); do
> >         tob $s.$method "$@" &
> >     done
>
> As far as I can tell, this is some incredibly stupid crap thrown together
> by an "object oriented" junkie to try to make one language look like some
> other language.  That is ALWAYS a bad idea.
>
> If you want to do a "method" to an "object", bash already provides a
> syntax for that:
>
>   method object
>
> Not:
>
>   object.method
>
> The latter is ass-backwards.  It's simply ludicrous.  Stop it.
>
> Now, look at this crap:
>
> >     for s in $(ls|shuf); do
>
> Do you know how hard we work every day to try to stamp out these sorts
> of bugs?  This is so bad I'm laugh/crying right now.
>
> touch 'this is a filename with spaces'
>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]