[26377] in Perl-Users-Digest
Perl-Users Digest, Issue: 8549 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Oct 20 14:05:35 2005
Date: Thu, 20 Oct 2005 11:05:04 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Thu, 20 Oct 2005 Volume: 10 Number: 8549
Today's topics:
Re: Microsoft Hatred FAQ axel@white-eagle.invalid.uk
Re: Microsoft Hatred FAQ <steve@REMOVETHIScyber.com.au>
Re: Modify patterns inside files <abigail@abigail.nl>
standardization efforts concerning xml-parser-outputs <nesselbosch@strato-rz.de>
Re: why the perl docs suck <ebohlman@omsdev.com>
Re: why the perl docs suck <darkon.tdo@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 20 Oct 2005 13:17:14 GMT
From: axel@white-eagle.invalid.uk
Subject: Re: Microsoft Hatred FAQ
Message-Id: <uNM5f.153113$RW.59193@fe2.news.blueyonder.co.uk>
In comp.lang.perl.misc Roedy Green <my_email_is_posted_on_my_website@munged.invalid> wrote:
> On Wed, 19 Oct 2005 03:15:03 -0700, "David Schwartz"
> <davids@webmaster.com> wrote or quoted :
>> Did I say their obligation was to secure their shareholders as much
>>profit as possible? I said their obligation was to their shareholders.
> You are literally saying people work for a company have an obligation
> to the shareholders. That is too obvious to be bothered with
> announcing. The employees take the shareholder's money, so obviously
> they have an obligation to produce something in return. When I read
> your words, I think you really mean this is the prime or sole
> obligation of an employee. I disagree with that. There are many
> loyalties that compete.
Employees have *no* obligations towards the shareholders of a company.
They are not employed or paid by the shareholders, they are employed
by the company itself which is a separate legal entity.
It is a different matter for the board of directors of a company.
Axel
------------------------------
Date: Thu, 20 Oct 2005 23:46:51 +1000
From: Steven D'Aprano <steve@REMOVETHIScyber.com.au>
Subject: Re: Microsoft Hatred FAQ
Message-Id: <pan.2005.10.20.13.46.50.253609@REMOVETHIScyber.com.au>
On Thu, 20 Oct 2005 13:17:14 +0000, axel wrote:
> Employees have *no* obligations towards the shareholders of a company.
> They are not employed or paid by the shareholders, they are employed
> by the company itself which is a separate legal entity.
>
> It is a different matter for the board of directors of a company.
The board of directors are also employees of the company. That's why the
company can fire them.
--
Steven.
------------------------------
Date: 20 Oct 2005 13:36:25 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Modify patterns inside files
Message-Id: <slrndlf7ap.96e.abigail@alexandra.abigail.nl>
ARIEL BOLUDOVSKY (boludovsky@hotmail.co.il) wrote on MMMMCDXXXIII
September MCMXCIII in <URL:news:Xns96F5697946EC7wanadoo@157.170.133.60>:
\\
\\ Hello,
\\
\\ I want to open a file, find a string, modify it, and then close the file.
\\
\\ open(FH, "+< $path1") or die "Opening: $!";
\\ @my_ARRAY = <FH>;
\\
\\ # change ARRAY here
\\
\\ seek(FH,0,0) or die "Seeking: $!";
\\ print FH @my_ARRAY or die "Printing: $!";
\\ truncate(FH,tell(FH)) or die "Truncating: $!";
\\ close(FH);
\\
\\ Can anyone describe a quick method to find and modify a given pattern?
Assuming the pattern doesn't cross line boundaries:
perl -i -pe 's/PATTERN/REPLACEMENT/' file
Abigail
--
sub _ {$_ = shift and y/b-yB-Y/a-yB-Y/ xor !@ _?
exit print :
print and push @_ => shift and goto &{(caller (0)) [3]}}
split // => "KsvQtbuf fbsodpmu\ni flsI " xor & _
------------------------------
Date: Thu, 20 Oct 2005 15:52:10 +0200
From: "jean-gert nesselbosch" <nesselbosch@strato-rz.de>
Subject: standardization efforts concerning xml-parser-outputs
Message-Id: <3rplobFkuq5cU1@uni-berlin.de>
hello everybody,
does anybody know of standardization efforts concerning the output
of w3cSchema/relaxNG-validating parsers ?
I use libxml2 for validation-purposes (w3c-Schema and relaxNG) and have
the impression that
(a) the output in case the xml-document is not valid, is not very verbose
(b) the structure of the returned message (in case of the xml-document
not beeing valid) is...well, it's just text. would be nice, if the
parser
would return some standardized xml
(c) there's no possibilty, neither in w3c-Schema nor in relaxNG (Schematron
is another case, but unfortunately I can't make use of it in the
environment
I'm programming for) to add "error_message-tags" to the schema file at
the appropriate places (at least not those that would be recognized by
the parser in case of a validation-error) containing self-explanatory
error-
messages, hints how to make the parsed xml-document valid....whatever.
right now, it seems to be (almost) impossible to automatically read the
output
of a validating parser, extract the important information and present it to
the
user.
gruss,
jean-gert
------------------------------
Date: 20 Oct 2005 14:47:18 GMT
From: Eric Bohlman <ebohlman@omsdev.com>
Subject: Re: why the perl docs suck
Message-Id: <Xns96F56556FFC3Aebohlmanomsdevcom@130.133.1.4>
"Fred@fred.net" <Fred@fred.net> wrote in
news:otldl1tcn1olhcmovghrih3t0j953i9nml@4ax.com:
> Imagine a world without rules.... it's not as ridiculous as it sounds.
> One of my favorite quotes is:
>
> "Do what thou wilt shall be the whole of the law."
Belief systems that incorporate such ideas usually qualify that sort of
statement with provisos that one's conduct not harm others.
An example of newsgroup conduct that does in fact harm others is the
asking of simple FAQs. When that happens, the people on the group who
know what they're talking about face a dilemma. Do they
1) Waste their time (which is usually part of their spare time) answering
the FAQ? If so, they have less time available to help people with
questions that can't be answered simply by reading the manual and that
require actual expertise. Harm's been done, as a valuable resource has
been made less available.
2) Ignore the post? If so, the history of this group shows that people
who don't know what they're talking about will chime in and give
incorrect or seriously incomplete answers. Harm's been done, as the
group has become a conduit for misinformation.
> I submit for consideration of everyone or no one that the guidelines
> for posting to this ng are so restrictive that deciding whether a
> certain post should be or should not be made is more tedious than
> solving the problem on one's own?
I can only wonder if you're reading the same guidelines as I am.
------------------------------
Date: Thu, 20 Oct 2005 15:29:16 -0000
From: "David K. Wall" <darkon.tdo@gmail.com>
Subject: Re: why the perl docs suck
Message-Id: <Xns96F574DC63E3Fdkwwashere@216.168.3.30>
Fred@fred.net <Fred@fred.net> wrote:
> I submit for consideration of everyone or no one that the
> guidelines for posting to this ng are so restrictive that deciding
> whether a certain post should be or should not be made is more
> tedious than solving the problem on one's own?
No. I've often run into problems when writing a Perl program and
thought of asking for help here. In the process of isolating the
problem enough to post a short but self-contained piece of code that
exhibits the problem I'm having, then explaining what I wanted to
happen versus what actually happened, I almost always find the source
of the problem on my own. I don't reread the guidelines every time I
have a question, I just try to write the sort of post *I* would want to
read. Pretty simple, really -- the guidelines are just a summary of
common sense and courtesy.
To repeat: following the guidelines will teach you -- if you don't
already know -- an approach to finding answers for yourself, a skill
more valuable than the answer to any specific question.
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 8549
***************************************
