Miles, Mon, Sep 24, 2007 at 08:21:42PM +0900, Miles Bader wrote: > > The reason we used "case" is that this has always been a builtin (has to > > be, because it changes workflow). > > > > Therefore I am somewhat uneasy that the patch went in so easily, > > especially given a message that flies in the face of our endeavours to > > make git less dependent on any given shell (as long as it is not broken to > > begin with). > > The comment "... holds only for a shell where [ is a builtin" doesn't > make any sense to me The 'while case ...' construct does not invoke any external commands. The 'while test ...' too, but only when 'test' is builtin. When 'test' is the external binary you get one additional fork/exec per each cycle. I believe that this trick comes from the old days where people were generally much more eager to save CPU cycles than now ;)) But if you tried to run Cygwin on the moderately new machines (like PIII), you still can notice that commands like 'man' are a bit slow just because they require a bunch of preprocessors (and processes in pipe) to run. So, "save the process, kill the fork/exec" ;)) > though: "-ne" is a standard operator even if "[" > isn't a builtin. It's useful if you are testing numbers in potentially > non-canonical form, e.g., with leading zeroes or something, and AFAIK is > quite portable. In general -- yes, it is portable and good for leading zeros. But in the case of $#, there will hardly be leading zeros or something else. And using '!=' typically saves you one atoi() + some other checks, since it typically translates to a bare strcmp(). -- Eygene - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
