login
Header Space

 
 

Re: Use PERL rather than C for system commands?

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Timothy L. Kay <tim@...>
Cc: <linux-activists@...>
Date: Thursday, January 16, 1992 - 3:28 am

It seems to me that the language PERL is ideal for implementing many
    of the pieces that are currently missing from Linux.  For example,
    init, getty, login, shutdown, halt, cron, inetd, etc. could very
    easily be written in PERL rather than C.  Most OS-support programs
    (including the ones mentioned previously) are not time critical.  They
    run very infrequently, and the performance degradation (if there is
    any) should be inconsequential.

Can't do standard library calls in perl :( - 
init, shutdown are definates 
getty - maybe                   
cron - probably want to use alarms for the next event, so no
inetd - we want to use listen, so no


    Third, I find PERL a *much* better script language than either sh or
    csh.

Agreed!  Let's get perl for Linux.

    Finally, PERL scripts are architecture-independent.  If Linux ever
    gets ported to multiple architectures (which I am guessing it will),
    all support programs written in PERL port with no effort at all.

Non-issue : any of the programs mentioned above, halt excepted (If we
are to code in an infinite loop with interrupts disabled) will go
no deeper than mayuking system calls.    
 
--------
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Use PERL rather than C for system commands?, Timothy L. Kay, (Thu Jan 16, 2:08 am)
Re: Use PERL rather than C for system commands? , Timothy L. Kay, (Thu Jan 16, 2:55 pm)
Re: PERL, Arlie Davis, (Thu Jan 16, 3:24 pm)
PERL, Peter MacDonald, (Thu Jan 16, 3:14 am)
Re: Use PERL rather than C for system commands? , , (Thu Jan 16, 3:28 am)
speck-geostationary