That's very true - which is why I tried to think of it as an event, a singular occurrence that can be pinpointed to one time and one environmental state, and why I continued, saying that we would have to search Larry Wall's mind for guidance if we didn't recognize this as Perl's first event (its initial emergence), since we would really have to go all the way back to when it was a flicker of imagination, through the many stages of name-picking and sort of self-identity establishment all the way to the release of v1.0. This point seems to me the foundation of Perl's ego, its social connectedness, sowing the seedlings of what was to become the Perl community. If we are to deny v1.0 this title, then even the name Perl could be considered a post-facto expansion of earlier names, attributions, and concepts. This, of course, is not to say that a thing's identity cannot change over time, as obviously Perl's has, but these observations just sit as so of a thread that seems to be woven through the versions in this one particular regard, a ghostly echo of times and versions past.

Bumbling always,
  -Adam

---

---

• 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.