|
Prev: Can "perldoc" take input from a pipe?
Next: Print a separator between each iteration of a foreach loop
From: Uri Guttman on 16 Apr 2008 13:42 >>>>> "SB" == Stephan Bour <sbour(a)niaid.nih.gov> writes: SB> Uri Guttman wrote: SB> } Stephan Bour <sbour(a)niaid.nih.gov> writes: SB> } > SB> } > Uri Guttman wrote: SB> } > SB> } > } why don't you just shut up about this already like you said you SB> } > SB> } > If you bothered to read the thread, he replied to someone who SB> } > replied before he did, so why focus this one single individual, SB> } > and waste a perfectly good post displaying you are incapable of SB> } > opening your mind to other possibilities instead of acting as if SB> } > all the FAQs, et al, are carved in granite. SB> } SB> } he was continuing when he said he wouldn't. he singled himself out. SB> So what? He was answering someone else, what concern is it of yours? Is SB> someone forcing you to read everything that comes down the pipe? Are you SB> unable to killfile a thread? and you? i am more concerned about proper perl training and answers. so when i see PERL used, i jump in. i also help out on many other questions here. do you? SB> } > } all the people who want to use PERL are those who never help SB> } > } others here. SB> } > SB> } > That's a rather broad statement, don'cha think? There is a certain SB> } > logic in rewriting `Practical Extraction and Report Language` as SB> } > `PERL` which is a common form of writing a term whose characters SB> } > each have a documented meaning, which would appear to be the case. SB> } SB> } and did you address my point? SB> I didn't know you had one. about your not helping. all you have done is jump in late into a stupid flame war and on the wrong side. SB> } do you help people here? i don't recall your name on many posts. SB> That's not what is or was of question, and is utterly irrelevant. Stop SB> invoking the straw-man. well, that shows how much you know. those who help have a say here. those who don't are not listened too. notice how all the PERL backers are not regular helpers here? that is the whole point. they aren't listening to what the community says about the names perl, Perl and PERL. SB> } it is simple. you help with real perl questions, you have a SB> } right to say stuff about this group. SB> And who decides who say what? You? I think not. Everyone has a SB> right to post in a public news group, and you have no right what SB> so ever to dictate otherwise. that comment is so common among those who never help here. hmm, that point again! so shut up unless you actually answer perl questions. that IS the reason for this group. flaming about PERL is not helping. and i can dictate all i want since i am the ruler of perl in my household. you want democracy, go learn python! you have been insulted. please crawl back into your cave and be quiet now. uri -- Uri Guttman ------ uri(a)stemsystems.com -------- http://www.sysarch.com -- ----- Perl Code Review , Architecture, Development, Training, Support ------ --------- Free Perl Training --- http://perlhunter.com/college.html --------- --------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
From: Keith Keller on 16 Apr 2008 14:26 On 2008-04-16, Uri Guttman <uri(a)stemsystems.com> wrote: > damn you x 2!! now you just gave more ammunition to the PERL crowd. they > will use the existance of a cpan module with PERL in its name as proof > that it is an acceptable form of the name. too bad they will be blind to > the root namespace of this module. I doubt it's clear to those who support PERL what the purpose of the Acme:: namespace is. --keith -- kkeller-usenet(a)wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information
From: Stephan Bour on 16 Apr 2008 14:49 Uri Guttman wrote: } "SB" == Stephan Bour <sbour(a)niaid.nih.gov> writes: } } > Uri Guttman wrote: } > } Stephan Bour <sbour(a)niaid.nih.gov> writes: } > } > } > } > Uri Guttman wrote: .... } > } > } all the people who want to use PERL are those who never help } > } > } others here. } > } > } > } > That's a rather broad statement, don'cha think? There is a } > } > certain logic in rewriting `Practical Extraction and Report } > } > Language` as `PERL` which is a common form of writing a term } > } > whose characters each have a documented meaning, which would } > } > appear to be the case. } } > } > } > } and did you address my point? } } > I didn't know you had one. } } about your not helping. all you have done is jump in late into a } stupid flame war and on the wrong side. 1) That's not what this is about nor is it a requirement to be able to comment. All that is required to comment on something is free will, whether you agree with that or not. 2) It was never a flame way until people like you jumped in and made it one out of your own distaste for the subject. .... } so shut up unless you actually answer perl questions. } that IS the reason for this group. flaming about PERL is not helping. The only one rubbing sticks together appears to be you, sir. All I saw coming from Mr. Etly's direction was a simple point. Any form of attack has been coming from you and some others who side with your point of view. It's a shame you refuse to see any other views than your own. } and i can dictate all i want since i am the ruler of perl in my } household. you want democracy, go learn python! 1) I thought it was `Perl` ? Please make up your mind? 2) A news group is no individuals house. Then again this makes about is much sense as anything else you spew. Stephan.
From: Gordon Etly on 16 Apr 2008 14:52 J�rgen Exner wrote: > "Stephan Bour" <sbour(a)niaid.nih.gov> wrote: >> `PERL` very well could correspond with `Practical Extraction >> and Report Language` > > It very well could and probably does. But what does that have to do > with the programming language named 'Perl'? It doesn't, but that was never my point. My point was simply the //usage// of "PERL" as a short hand for that expansion. I hope this is clear now :) -- G.Etly
From: Charlton Wilbur on 16 Apr 2008 14:23 >>>>> "SB" == Stephan Bour <sbour(a)niaid.nih.gov> writes: SB> It maybe a joke to *you* but your opinion doesn't change what SB> it says in the applicable doc. To wit: But never write "PERL", because perl is not an acronym, apocryphal folklore and post‐ facto expansions notwithstanding. It seems to me that the FAQ is as applicable a document as the manpage. Or do you have some hermeneutic grounds for claiming that the manpage is more important? SB> } If you want to engage with those knowlegeable in a subject, SB> } you should adopt their conventions. If not....your call... SB> So, `my way or the hiway`? Are you saying no one may question SB> rules, conventions, and ideals? Is this really the way you SB> feel a community should function? No, he's saying that this point has been questioned many times and it has thus far always been decided in favor of the side you're arging against. Consider the use of 'of' in the place of 'have', as in 'I should of gone to the bank yesterday.' It's a common error, and it's possible to make a case for its acceptance; it's certainly popular enough, and most people know what it means. However, it's still incorrect, and using it will mark you in the eyes of literate people as either careless or ignorant. So it is with 'PERL' -- using 'PERL' won't cause comprehension problems, but it will mark you as either a novice who's still largely ignorant of the rudiments of Perl or as a crank who'd rather argue over trivialities in order to preserve his self-image as an iconoclastic free thinker. And, you know, being resistant to the FAQ's tutelage on a matter such as PERL versus Perl versus perl means you're also likely to be resistant to its elucidation of the problems with always quoting "$vars", or with numeric representation problems, or with the problems with symbolic references. But if you want to come across as a novice or a crank, by all means, feel free. You've now had ample fair warning. Charlton -- Charlton Wilbur cwilbur(a)chromatico.net
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: Can "perldoc" take input from a pipe? Next: Print a separator between each iteration of a foreach loop |