I don't think it's off the wall to assume that what's good enough for my distribution's purposes is good enough for mine

Except that my take on this is that, whereas "bash" is being provided primarily for *you* to use, "perl" is there primarily because the system needs it.

And you *are* quite free to "assume that what's good enough for my distribution's purposes is good enough for mine". It's your right to complain about the fact that your assumption is in error that I'm not so sure about :-)

Why use the system's libc?

I don't know ... probably for convenience ... which presumably is the same reason that you'd use the system's perl. But, having accepted the system's libc, I don't think you can then go and complain about it (unless it has been jiggered with in a way that contravenes the license under which it is distributed). Same goes for the system's perl.

Cheers,
Rob

---

---

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