My point wasn't that google caches it. My point was that the link is to a copyrighted work of Larry Wall et al, via O'Rielly (who quite likely actualy owns the copyright, but I'm too tired and drunk to check), which they have expressedly not given permission to distribte. My complaint isn't at Google, who is just doing their level best to provide relevant search results and related services (which they do very well), but at the people who put a copy of Programing Perl on a publicly-accessable web-site, in voilation of it's copyright. (I suspect the people in question bought a site license for the CD bookshelf or O'Rielly Safari, but I'm quite certianly not at their site.)
Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).
-
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.
|
