[EMAIL PROTECTED] wrote:

> >From: [EMAIL PROTECTED] (Bill Davidsen)
> 
> >[EMAIL PROTECTED] wrote:
> 
> >> >From: [EMAIL PROTECTED] (Bill Davidsen)
> >>
> >> >"Mike A. Harris" <[EMAIL PROTECTED]> wrote:
> >>
> >> >> /usr/bin/which is an ELF executable on Red Hat Linux, but I agree
> >> >> that it definitely is not an application that can be expected to
> >> >> be portable.
> >>
> >> >  One of the reasons bash added 'type' as a builtin.
> >> 
> >> "Type"  is a shell builtin at least since 1982.
> 
> >  I didn't know bash had been around that long, but why is the date
> >relevant to the choice to include the feature when designing bash?
> 
> This is funny.... you write a statement that is close to 'bash invented
> "type"' and don"t understand when I tell you that type is a stone age
> command.
    
I still don't see why the date matters. When the design was done, some
existing features like 'type' were included, some were left out, and
some were slightly changed or enhanced. I don't see anywhere that I made    
any statement at all about invention, only that the feature was chosen    
for inclusion. We were talking about shells and 'which,' not sure what
you're talking about. For some reason you seem to think that the date is
very important, but I think it's also wrong, bash isn't that old.
  
--
   -bill davidsen ([EMAIL PROTECTED])
"The secret to procrastination is to put things off until the
 last possible moment - but no longer"  -me
[EMAIL PROTECTED] wrote:

> >From: [EMAIL PROTECTED] (Bill Davidsen)
> 
> >[EMAIL PROTECTED] wrote:
> 
> >> >From: [EMAIL PROTECTED] (Bill Davidsen)
> >>
> >> >"Mike A. Harris" <[EMAIL PROTECTED]> wrote:
> >>
> >> >> /usr/bin/which is an ELF executable on Red Hat Linux, but I agree
> >> >> that it definitely is not an application that can be expected to
> >> >> be portable.
> >>
> >> >  One of the reasons bash added 'type' as a builtin.
> >> 
> >> "Type"  is a shell builtin at least since 1982.
> 
> >  I didn't know bash had been around that long, but why is the date
> >relevant to the choice to include the feature when designing bash?
> 
> This is funny.... you write a statement that is close to 'bash invented
> "type"' and don"t understand when I tell you that type is a stone age
> command.
    
I still don't see why the date matters. When the design was done, some
existing features like 'type' were included, some were left out, and
some were slightly changed or enhanced. I don't see anywhere that I made    
any statement at all about invention, only that the feature was chosen    
for inclusion. We were talking about shells and 'which,' not sure what
you're talking about. For some reason you seem to think that the date is
very important, but I think it's also wrong, bash isn't that old.
  
--
   -bill davidsen ([EMAIL PROTECTED])
"The secret to procrastination is to put things off until the
 last possible moment - but no longer"  -me


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to