I fear that if perl as it is known today had been around in the sixties, it would have fallen into such severe disrepute that nobody would be using it today. Back then, every byte of memory that you could save counted. perl uses a *lot* more memory that the languages available in the sixties. It does so for good reasons, and the trade-off is well worth it now in this decadent era of cheap DDR SDRAM and many-gigabyte hard drives, but it would have been a different thing in the sixties. Look at the reputation Lisp got, and it didn't have anything like as much memory overhead as perl. Even as late as the mid eighties it was still considered reasonable to store eight boolean variables in a single byte, in order to conserve RAM. It meant an extra couple of clock cycles (also at a premium back then) to examine or change any of them, but it saved seven whole bytes of RAM, so people did it. Indeed, Infocom's ubiquitous zmachine (almost certainly the most portable and widely-implemented virtual machine in the history of computing) has this feature (variables that are actually stored in a single bit) hardwired into its object data structure.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|