Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #31286

Re: About reader-writer mechanisms

Show all headers | View raw

On 3/8/2015 12:05 AM, Ramine wrote:
> As you have noticed, currently , I have implemented my algorithm for
> Delphi and FreePascal compilers...

Someone who cannot take care to write more than one sentence without 
encountering a grammatical or spelling error has code that cannot be 
trusted.

Someone who believes that Pascal/Delphi is topical in a Java newsgroup 
has code that cannot be trusted.

Someone who has repeatedly violated netiquette has code that cannot be 
trusted.

Someone who has repeatedly lied cannot be trusted in general, and 
therefore has code that cannot be trusted.

Someone who claims existing multithreaded code is not scalable, claims 
to have nothing better, and offers nothing more than his or her own word 
in evidence of this fact definitely has code that cannot be trusted.

...

Since there is so much evidence of distrust in this code, I can only 
reasonably conclude that the code is malware (or at best, an invitation 
for malware) and therefore am obliged to submit signatures of it to the 
appropriate AV vendors to save others' computers. If you're reading his 
far and you're still wondering how this might be avoided in the future, 
then I can only recommend going back to school, for you obviously lack 
reading comprehension ability. :-)

> You can download my scalable SeqlockX and read about the algorithm from:
[Snip URL of obvious malware]

-- 
Beware of bugs in the above code; I have only proved it correct, not 
tried it. -- Donald E. Knuth

Back to comp.lang.java.programmer | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: About reader-writer mechanisms Joshua Cranmer 🐧 <Pidgeot18@verizon.invalid> - 2015-03-08 00:03 -0600
  Re: About reader-writer mechanisms Jerry Stuckle <jstucklex@attglobal.net> - 2015-03-08 16:44 -0400

csiph-web