Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #375257 > unrolled thread
| Started by | DFS <nospam@dfs.com> |
|---|---|
| First post | 2016-10-06 11:42 -0400 |
| Last post | 2016-10-07 11:10 -0700 |
| Articles | 20 on this page of 109 — 20 participants |
Back to article view | Back to comp.os.linux.advocacy
Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-06 11:42 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Adlbifhr Mjduhgfks <am@random.us> - 2016-10-06 20:00 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-06 19:31 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-07 00:20 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-06 20:55 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-07 01:04 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-06 22:11 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-07 02:19 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-06 23:20 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-07 03:33 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-07 00:02 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-07 04:22 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children fr314159@gmail.com - 2016-10-07 08:08 -0700
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-07 10:42 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-08 03:13 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-08 03:19 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-10-08 05:37 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-10 07:09 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children Melzzzzz <mel@zzzzz.com> - 2016-10-10 14:11 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-10 07:37 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-10 16:56 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Silver Slimer <.m@nsn.s> - 2016-10-08 10:26 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-08 10:48 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Steve Carroll <fretwizzer@gmail.com> - 2016-10-08 07:58 -0700
Re: Ping sbd: another programming challenge for your developmentally challenged children Silver Slimer <.m@nsn.s> - 2016-10-08 15:04 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-09 10:24 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-08 15:28 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-10-08 15:41 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-08 19:57 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Silver Slimer <.m@nsn.s> - 2016-10-08 17:23 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Silver Slimer <.m@nsn.s> - 2016-10-08 10:24 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-08 10:44 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-08 17:11 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-08 13:46 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-08 20:01 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children ronb <ronb02NOSPAM@gmail.com> - 2016-10-08 23:23 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-10-08 20:43 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-09 01:15 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-09 01:13 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children ronb <ronb02NOSPAM@gmail.com> - 2016-10-09 02:08 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-09 02:13 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-10-09 08:15 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-10 07:27 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children ronb <ronb02NOSPAM@gmail.com> - 2016-10-08 23:22 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-08 22:54 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-09 15:13 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-09 18:14 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-09 16:19 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-09 18:25 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-10 07:21 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-10 10:50 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children Snit <usenet@gallopinginsanity.com> - 2016-11-01 10:09 -0700
Re: Ping sbd: another programming challenge for your developmentally challenged children William Poaster <wp@dev.null> - 2016-10-09 22:29 +0100
Re: Ping sbd: another programming challenge for your developmentally challenged children Marek Novotny <marek.novotny@marspolar.com> - 2016-10-09 13:38 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-09 23:58 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-10 07:29 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children William Poaster <wp@dev.null> - 2016-10-10 13:41 +0100
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-10 12:25 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-10 13:33 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-10 10:51 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children chrisv <chrisv@nospam.invalid> - 2016-10-10 12:45 -0500
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-10 16:35 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children Silver Slimer <.m@nsn.s> - 2016-10-10 18:54 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-10 21:56 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-10 22:48 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Jim Polaski <jpolaski@linuxmail.org> - 2016-10-11 00:02 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-10 21:58 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children GreyCloud <Cumulus@mist.com> - 2016-10-10 21:58 -0600
Re: Ping sbd: another programming challenge for your developmentally challenged children Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-07 17:56 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-07 13:25 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Adlbifhr Mjduhgfks <am@random.us> - 2016-10-08 00:12 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-08 10:40 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-10 13:34 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-07 04:15 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Sandman <mr@sandman.net> - 2016-10-07 16:37 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-07 20:34 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children Steve Carroll <frelwizzen@gmail.com> - 2016-10-07 11:10 -0700
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-20 11:20 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-21 08:53 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Melzzzzz <mel@zzzzz.com> - 2016-10-21 13:19 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-21 10:45 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-22 01:06 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Melzzzzz <Melzzzzz@zzzzz.com> - 2016-10-22 02:15 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-22 02:40 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Melzzzzz <mel@zzzzz.com> - 2016-10-22 05:00 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-22 16:34 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Melzzzzz <mel@zzzzz.com> - 2016-10-22 23:14 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-10-22 18:24 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-25 23:20 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-26 05:22 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-26 11:26 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-26 20:42 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Melzzzzz <mel@zzzzz.com> - 2016-10-27 01:45 +0200
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-27 01:21 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-22 09:33 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children deplorable owl <owl@rooftop.invalid> - 2016-10-22 16:50 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-06 21:25 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Sandman <mr@sandman.net> - 2016-10-07 16:30 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Steve Carroll <fretwizzer@gmail.com> - 2016-10-07 09:44 -0700
Re: Ping sbd: another programming challenge for your developmentally challenged children Sandman <mr@sandman.net> - 2016-10-07 17:20 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-07 15:24 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Sandman <mr@sandman.net> - 2016-10-07 20:01 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-07 16:50 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Sandman <mr@sandman.net> - 2016-10-07 21:37 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-07 17:54 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Sandman <mr@sandman.net> - 2016-10-07 22:11 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children DFS <nospam@dfs.com> - 2016-10-07 13:51 -0400
Re: Ping sbd: another programming challenge for your developmentally challenged children Sandman <mr@sandman.net> - 2016-10-07 18:13 +0000
Re: Ping sbd: another programming challenge for your developmentally challenged children Steve Carroll <frelwizzen@gmail.com> - 2016-10-07 11:10 -0700
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
| From | chrisv <chrisv@nospam.invalid> |
|---|---|
| Date | 2016-10-10 12:45 -0500 |
| Message-ID | <s8knvbl0ls79a8aj8iaddu71up6jgkcuc7@4ax.com> |
| In reply to | #375644 |
ronb wrote: > some piece of shit wrote: >> >> It just doesn't make any sense to use one. How can they advocate with a >> killfile? Hey, "GreyCloud", have you figured-out, yet, that Windows newsreaders also have kill-file capability? Ignorant old coot. >By ignoring the repetitious idiocy by drones like "Snit." And ignoring the braying of jackasses like "GreyCloud". Did you know that that lying POS once declared it the "epitome of hypocrisy" for FOSS advocates to participate in a moderated forum? Apparently the stupid POS thinks that "freedom" means that you can't have private meetings, away from assholes like him. You must give the assholes the "freedom" to harass and disrupt. -- "Of course they'll always say they use kill files, but how can they if they are using windows?" - "GreyCloud", putting his ignorance on display
[toc] | [prev] | [next] | [standalone]
| From | GreyCloud <Cumulus@mist.com> |
|---|---|
| Date | 2016-10-10 16:35 -0600 |
| Message-ID | <nth538$5er$1@dont-email.me> |
| In reply to | #375854 |
chrisv wrote: > ronb wrote: > >> some piece of shit wrote: >>> >>> It just doesn't make any sense to use one. How can they advocate with a >>> killfile? > > Hey, "GreyCloud", have you figured-out, yet, that Windows newsreaders > also have kill-file capability? Ignorant old coot. > >>By ignoring the repetitious idiocy by drones like "Snit." > > And ignoring the braying of jackasses like "GreyCloud". > > Did you know that that lying POS once declared it the "epitome of > hypocrisy" for FOSS advocates to participate in a moderated forum? > > Apparently the stupid POS thinks that "freedom" means that you can't > have private meetings, away from assholes like him. You must give the > assholes the "freedom" to harass and disrupt. > But you just love to troll, don't you. I'm using Linux, so I thought you would've at least read the headers by now.
[toc] | [prev] | [next] | [standalone]
| From | Silver Slimer <.m@nsn.s> |
|---|---|
| Date | 2016-10-10 18:54 -0400 |
| Message-ID | <nth66n$93a$1@dont-email.me> |
| In reply to | #375870 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-10-10 6:35 PM, GreyCloud wrote: > chrisv wrote: > >> ronb wrote: >> >>> some piece of shit wrote: >>>> >>>> It just doesn't make any sense to use one. How can they >>>> advocate with a killfile? >> >> Hey, "GreyCloud", have you figured-out, yet, that Windows >> newsreaders also have kill-file capability? Ignorant old coot. >> >>> By ignoring the repetitious idiocy by drones like "Snit." >> >> And ignoring the braying of jackasses like "GreyCloud". >> >> Did you know that that lying POS once declared it the "epitome >> of hypocrisy" for FOSS advocates to participate in a moderated >> forum? >> >> Apparently the stupid POS thinks that "freedom" means that you >> can't have private meetings, away from assholes like him. You >> must give the assholes the "freedom" to harass and disrupt. >> > > But you just love to troll, don't you. I'm using Linux, so I > thought you would've at least read the headers by now. Nobody will ever be good enough for hypochrisv. He's the moral authority here, don't forget, and only _he_ will determine who is allowed to be recognized as a Linux user. He also determines who is cool enough to be his friend though so far, not only person has applied for that position. - -- Silver Slimer Islam is a disease Gab.AI: @silverslimer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX/BwmAAoJEIwFfgf/rr+uS2gH/jlGoaJEkJIgM+DWUdH+xhLZ ufCDr8beXkkiOd/X/c5PHZEIeujubaUPew+vsTQJSRZDmtTAbmr+Zq5jnL4TvmfS WaLd6JdRzMP/wNZWoc58SY1cXAVe9NbaWk6KWxwQQe2xcibP9W9EEuPu9J1orjRG GhSVcvqdOFBVUsSEsGQ/U9kOCI2gS4EWeqaFhIImNbSYIS1PSYDWp5VCZ61ksNWf tY8QNEqZYld0c+iz8fb6Ggzoe5drh+U7G/Q36YxG3iD0Nf6jmW7NC2FOz7SqVzir FYUyxiUYxMou0g/EqUBUWfwGQGP852cuBFdIVAVw0f4KmdcYyz+nPfEuQP6TzfY= =QIqZ -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | GreyCloud <Cumulus@mist.com> |
|---|---|
| Date | 2016-10-10 21:56 -0600 |
| Message-ID | <nthns2$cac$1@dont-email.me> |
| In reply to | #375873 |
Silver Slimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 2016-10-10 6:35 PM, GreyCloud wrote: >> chrisv wrote: >> >>> ronb wrote: >>> >>>> some piece of shit wrote: >>>>> >>>>> It just doesn't make any sense to use one. How can they >>>>> advocate with a killfile? >>> >>> Hey, "GreyCloud", have you figured-out, yet, that Windows >>> newsreaders also have kill-file capability? Ignorant old coot. >>> >>>> By ignoring the repetitious idiocy by drones like "Snit." >>> >>> And ignoring the braying of jackasses like "GreyCloud". >>> >>> Did you know that that lying POS once declared it the "epitome >>> of hypocrisy" for FOSS advocates to participate in a moderated >>> forum? >>> >>> Apparently the stupid POS thinks that "freedom" means that you >>> can't have private meetings, away from assholes like him. You >>> must give the assholes the "freedom" to harass and disrupt. >>> >> >> But you just love to troll, don't you. I'm using Linux, so I >> thought you would've at least read the headers by now. > > Nobody will ever be good enough for hypochrisv. He's the moral > authority here, don't forget, and only _he_ will determine who is > allowed to be recognized as a Linux user. He also determines who is > cool enough to be his friend though so far, not only person has > applied for that position. > The guy is in no position to be in anyway of authority. He's nuts.
[toc] | [prev] | [next] | [standalone]
| From | "Octavian W. Lagrange" <olagrang@perch.invalid> |
|---|---|
| Date | 2016-10-10 22:48 +0000 |
| Message-ID | <hjgaso03.gae@perch.invalid> |
| In reply to | #375854 |
chrisv <chrisv@nospam.invalid> wrote: > ronb wrote: > >> some piece of shit wrote: >>> >>> It just doesn't make any sense to use one. How can they advocate with a >>> killfile? > > Hey, "GreyCloud", have you figured-out, yet, that Windows newsreaders > also have kill-file capability? Ignorant old coot. > You're definitely the man to clue us in about killfiles and Windows newsreaders. You should try Linux sometime though. I'm sure GreyCloud wouldn't mind helping you get started.
[toc] | [prev] | [next] | [standalone]
| From | Jim Polaski <jpolaski@linuxmail.org> |
|---|---|
| Date | 2016-10-11 00:02 +0000 |
| Message-ID | <e62ofoFmtnfU3@mid.individual.net> |
| In reply to | #375872 |
On 2016-10-10, Octavian W. Lagrange <olagrang@perch.invalid> wrote: > chrisv <chrisv@nospam.invalid> wrote: >> ronb wrote: >> >>> some piece of shit wrote: >>>> >>>> It just doesn't make any sense to use one. How can they advocate with a >>>> killfile? >> >> Hey, "GreyCloud", have you figured-out, yet, that Windows newsreaders >> also have kill-file capability? Ignorant old coot. >> > > You're definitely the man to clue us in about killfiles and > Windows newsreaders. You should try Linux sometime though. > I'm sure GreyCloud wouldn't mind helping you get started. She (chrisv) has to be a troll.
[toc] | [prev] | [next] | [standalone]
| From | GreyCloud <Cumulus@mist.com> |
|---|---|
| Date | 2016-10-10 21:58 -0600 |
| Message-ID | <ntho10$cac$3@dont-email.me> |
| In reply to | #375882 |
Jim Polaski wrote: > On 2016-10-10, Octavian W. Lagrange <olagrang@perch.invalid> wrote: >> chrisv <chrisv@nospam.invalid> wrote: >>> ronb wrote: >>> >>>> some piece of shit wrote: >>>>> >>>>> It just doesn't make any sense to use one. How can they advocate with a >>>>> killfile? >>> >>> Hey, "GreyCloud", have you figured-out, yet, that Windows newsreaders >>> also have kill-file capability? Ignorant old coot. >>> >> >> You're definitely the man to clue us in about killfiles and >> Windows newsreaders. You should try Linux sometime though. >> I'm sure GreyCloud wouldn't mind helping you get started. > > She (chrisv) has to be a troll. A reverse troll as she never uses linux and tries to make linux look bad.
[toc] | [prev] | [next] | [standalone]
| From | GreyCloud <Cumulus@mist.com> |
|---|---|
| Date | 2016-10-10 21:58 -0600 |
| Message-ID | <nthnvs$cac$2@dont-email.me> |
| In reply to | #375872 |
Octavian W. Lagrange wrote: > chrisv <chrisv@nospam.invalid> wrote: >> ronb wrote: >> >>> some piece of shit wrote: >>>> >>>> It just doesn't make any sense to use one. How can they advocate with a >>>> killfile? >> >> Hey, "GreyCloud", have you figured-out, yet, that Windows newsreaders >> also have kill-file capability? Ignorant old coot. >> > > You're definitely the man to clue us in about killfiles and > Windows newsreaders. You should try Linux sometime though. > I'm sure GreyCloud wouldn't mind helping you get started. It's easy to do, but I doubt she wants to run linux. Hypochrisv loves to use windows and his headers are proof of that. Shes' never run linux that I know of.
[toc] | [prev] | [next] | [standalone]
| From | Peter Köhlmann <peter-koehlmann@t-online.de> |
|---|---|
| Date | 2016-10-07 17:56 +0200 |
| Message-ID | <nt8gic$cjs$1@dont-email.me> |
| In reply to | #375428 |
fr314159@gmail.com wrote: > On Friday, October 7, 2016 at 12:22:17 AM UTC-4, Octavian W. Lagrange > wrote: > >> >> It only spaces down, not up. It's retarded. >> > > Why are you being so chummy with this contemptible idiot? > > He is the friggin' enemy! No, he is not. He is a windows user afraid of losing his preferred platform over the years.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2016-10-07 13:25 -0400 |
| Message-ID | <nt8lpe$a4$2@dont-email.me> |
| In reply to | #375431 |
On 10/7/2016 11:56 AM, Peter Köhlmann wrote: > fr314159@gmail.com wrote: > >> On Friday, October 7, 2016 at 12:22:17 AM UTC-4, Octavian W. >> Lagrange wrote: >> >>> >>> It only spaces down, not up. It's retarded. >>> >> >> Why are you being so chummy with this contemptible idiot? >> >> He is the friggin' enemy! > > No, he is not. He is a windows user afraid of losing his preferred > platform over the years. Except for the painful loss of MS Office, I could easily make a transition to Linux. For a while now I've mainly written python and pyodbc code for SQLite and other databases. Pretty soon I'm gonna start using Linux and C and gcc and try to work thru the entire 'Advanced Programming in the Unix Environment (2nd Ed)' book. Probably take a year off and on. I say try because it's difficult material. (I got that book for $11 at thriftbooks.com - in great condition, too)
[toc] | [prev] | [next] | [standalone]
| From | Adlbifhr Mjduhgfks <am@random.us> |
|---|---|
| Date | 2016-10-08 00:12 +0000 |
| Message-ID | <nt9dla01cc@news4.newsguy.com> |
| In reply to | #375439 |
On Fri, 07 Oct 2016 13:25:17 -0400, DFS wrote: > > Pretty soon I'm gonna start using Linux and C and gcc and try to work > thru the entire 'Advanced Programming in the Unix Environment (2nd Ed)' > book. Probably take a year off and on. I say try because it's > difficult material. > Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha! The dumb-fuck shill wants to learn C programming! That's rich! Well, the BEST way to learn C, and perhaps the ONLY way, is to first learn Intel assembly language programming. C fits the machine like a glove and one must know the actual language of the machine. But perhaps it will suffice to first master the machine interface itself, that is, the Application Binary Interface (ABI): https://www.uclibc.org/docs/psABI-x86_64.pdf (That goddamned abi-0.99.7 is HARD to locate since www.x86-64.org went down.) EVERYTHING that happens on modern hardware MUST conform to this spec. Keep in mind that the calling conventions differ markedly between GNU/Linux and Microshit. Why they even granted Microshit a convention of its own is the height of lunacy.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2016-10-08 10:40 -0400 |
| Message-ID | <ntb0fm$s4i$1@dont-email.me> |
| In reply to | #375503 |
On 10/7/2016 8:12 PM, Adlbifhr Mjduhgfks wrote: > On Fri, 07 Oct 2016 13:25:17 -0400, DFS wrote: > >> >> Pretty soon I'm gonna start using Linux and C and gcc and try to work >> thru the entire 'Advanced Programming in the Unix Environment (2nd Ed)' >> book. Probably take a year off and on. I say try because it's >> difficult material. >> > > Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha! The dumb-fuck shill > wants to learn C programming! That's rich! I already know a little. This is most everything I wrote (all on Linux): http://s000.tinyupload.com/index.php?file_id=22877893461853770050 > Well, the BEST way to learn C, and perhaps the ONLY way, is > to first learn Intel assembly language programming. C fits > the machine like a glove and one must know the actual language > of the machine. You once recommended "Introduction to 64 Bit Assembly Language Programming For Linux" by Ray Seyfarth (2011 - 1st edition) I found a .pdf and will take a look at it. I looked at his site. He lives in Hattiesburg MS, the same city my Mom was born in. His Google+ page has some interesting posts https://plus.google.com/116386239661476506843 > But perhaps it will suffice to first master the machine interface > itself, that is, the Application Binary Interface (ABI): > > https://www.uclibc.org/docs/psABI-x86_64.pdf > > (That goddamned abi-0.99.7 is HARD to locate since www.x86-64.org > went down.) Notice their email addresses on the first page Edited by Michael Matz 1, Jan Hubiˇcka 2, Andreas Jaeger 3, Mark Mitchell 4 November 17, 2014 1 matz@suse.de 2 jh@suse.cz 3 aj@suse.de 4 mark@codesourcery.com > EVERYTHING that happens on modern hardware MUST conform to this > spec. > > Keep in mind that the calling conventions differ markedly between > GNU/Linux and Microshit. Why they even granted Microshit a convention > of its own is the height of lunacy. That's the power of 1+ billion users. I do remember how easy it was to start writing C on Linux. * write code in editor, save file * compile: gcc -Wall isSQLiteDB.c -o isSQLiteDB * run ./isSQLiteDB test.db text.txt I used Geany and liked it pretty well.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2016-10-10 13:34 -0400 |
| Message-ID | <ntgjeb$2ji$3@dont-email.me> |
| In reply to | #375503 |
On 10/7/2016 8:12 PM, Adlbifhr Mjduhgfks wrote: > https://www.uclibc.org/docs/psABI-x86_64.pdf > > (That goddamned abi-0.99.7 is HARD to locate since www.x86-64.org > went down.) I sent Michael Matz an email: <quote> DFS: Is there a later version? Matz:. Normally a subversion repository at http://www.x86-64.org/svn/trunk/x86-64-ABI/ contains the latest official sources, but now that you ask I see that server doesn't respond currently. I'll try to find a responsible person. DFS: Is there an official site it's hosted on? Matz: Not anymore. H.J. Lu keeps a copy of the repo in git form plus generated PDFs from various branches at his github page: https://github.com/hjl-tools/x86-psABI/wiki/X86-psABI (It also contains an updated x86-32 and an MCU psABI). That wiki page also refers to some google groups for discussions. </quote>
[toc] | [prev] | [next] | [standalone]
| From | "Octavian W. Lagrange" <olagrang@perch.invalid> |
|---|---|
| Date | 2016-10-07 04:15 +0000 |
| Message-ID | <ahjdfie03.a@perch.invalid> |
| In reply to | #375389 |
Octavian W. Lagrange <olagrang@perch.invalid> wrote:
> DFS <nospam@dfs.com> wrote:
>> Also, I notice your fmt output doesn't retain the 2 spaces after a
>> period. That seems strange.
>>
>
> fmt has a -u option that is supposed to handle that, but it does
> not seem to work. You may have uncovered a bug.
>
> -u, --uniform-spacing
> one space between words, two after sentences
>
info fmt has slightly different wording:
‘-u’
‘--uniform-spacing’
Uniform spacing. Reduce spacing between words to one space, and
spacing between sentences to two spaces.
So it only *reduces* to a proper spacing. It will not increase to
two spaces between sentences. Pretty stupid if you ask me. And
also a misleading manpage.
[toc] | [prev] | [next] | [standalone]
| From | Sandman <mr@sandman.net> |
|---|---|
| Date | 2016-10-07 16:37 +0000 |
| Message-ID | <sandman-e04dd96077b2bd6fe4fa93bd5c35bf95@individual.net> |
| In reply to | #375391 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article <ahjdfie03.a@perch.invalid>, Octavian W. Lagrange wrote: > > > DFS: > > > Also, I notice your fmt output doesn't retain the 2 spaces after > > > a period. That seems strange. > > > > Octavian W. Lagrange: > > fmt has a -u option that is supposed to handle that, but it does > > not seem to work. You may have uncovered a bug. > > > -u, --uniform-spacing > > one space between words, two after sentences > > info fmt has slightly different wording: > ‘-u’ ‘--uniform-spacing’ Uniform spacing. Reduce spacing > between words to one space, and spacing between sentences to two > spaces. > So it only *reduces* to a proper spacing. It will not increase to > two spaces between sentences. Pretty stupid if you ask me. And > also a misleading manpage. Is this an American thing? No one does this where I come from. But then again, we don't put interpunction inside parenthesises like you guys seem to do a lot (like this.) And not (like this). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJX9883AAoJECFEwfBaA+jRD5AIALi70Owx45NKOgsrQCuG+aog 6f0UwiFF4MAY3o6RLpZF/WlVU1ncODbEhwskpByA6TXx58EYYIcIvwBpIwvcIjFW 2GrUNY2u2XW4dnyLlhnzH3Y4VaPpZrKporzK2hafXcWPtfPJi40cajmtS8/wUsIO dl6eB2IKCBvp3rApP4aQALq1dM85CU4bWxCE8hE+vXtdj1HteWh+pbCPDSLnlmQ3 uOoagBuG7aWSe/BObRF+Y8Ss9Exw89WZvrbwVG4vT7MHuKO80deQR96J2fm45NS2 ZuXbFdy9POBPIW2wHD0zyXEAOxpgaK8oh8yV79fzeQP355FIcrP1RcDpSscLKH8= =RShG -----END PGP SIGNATURE----- -- Sandman
[toc] | [prev] | [next] | [standalone]
| From | Peter Köhlmann <peter-koehlmann@t-online.de> |
|---|---|
| Date | 2016-10-07 20:34 +0200 |
| Message-ID | <nt8prl$fri$1@dont-email.me> |
| In reply to | #375435 |
Sandman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In article <ahjdfie03.a@perch.invalid>, Octavian W. Lagrange wrote: > >> > > DFS: >> > > Also, I notice your fmt output doesn't retain the 2 spaces after >> > > a period. That seems strange. >> > >> > Octavian W. Lagrange: >> > fmt has a -u option that is supposed to handle that, but it does >> > not seem to work. You may have uncovered a bug. >> >> > -u, --uniform-spacing >> > one space between words, two after sentences >> >> info fmt has slightly different wording: > >> ‘-u’ ‘--uniform-spacing’ Uniform spacing. Reduce spacing >> between words to one space, and spacing between sentences to two >> spaces. > >> So it only *reduces* to a proper spacing. It will not increase to >> two spaces between sentences. Pretty stupid if you ask me. And >> also a misleading manpage. > > Is this an American thing? No one does this where I come from. But then > again, we don't put interpunction inside parenthesises like you guys seem > to do a lot (like this.) And not (like this). > Same in germany. It is considered bad grammar if you put 2 spaces after interpunction. And putting interpunction into parentheses like that is considered as an error
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2016-10-07 11:10 -0700 |
| Message-ID | <e118d9b3-b788-4ee4-b78b-4fe77ee83cbb@googlegroups.com> |
| In reply to | #375362 |
On Thursday, October 6, 2016 at 5:55:49 PM UTC-7, DFS wrote:
> On 10/6/2016 8:20 PM, Octavian W. Lagrange wrote:
> > DFS <nospam@dfs.com> wrote:
> >> On 10/6/2016 4:00 PM, Adlbifhr Mjduhgfks wrote:
> >>
> >>
> >>> I will not waste my time writing actual code
> >>
> >>
> >> Of course you won't, because you'll fuck it up and your incompetence
> >> will once again be on full display.
> >>
> >
> > bash one-liner. pwned.
> > fmt -w <width> <file>|nl -v <start> -n ln|awk '{printf $1;$1=""; print " >" $0}'
>
>
> nah.
>
> You cheated with fmt and nl.
If Snit did it he would cheat with Automator and mouse scripting.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2016-10-20 11:20 -0400 |
| Message-ID | <nuanc6$909$2@dont-email.me> |
| In reply to | #375308 |
On 10/6/2016 4:00 PM, Adlbifhr Mjduhgfks wrote:
> Furthermore, the dumb fuck is actually manipulating strings,
> which always is a computationally very expensive undertaking.
My original code executed the join() string operation once for each word
in the input (78), plus once per line of screen output (8 more), for a
total of 86 per run. Sounds like a lot.
So I wrote a new routine that eliminated all but the 8 join() outputs to
screen. It keeps a running total of the length of words (elements in
the list), and when that total meets or exceeds the block size, it
join()s the applicable elements and writes the line to screen.
Basically:
* original code join()s strings then evaluates length.
* new code evaluates lengths of the strings then does join().
The output of the two is identical.
----------------------------------------------------------------------
import sys,time
def split_ORIG(t,n,m):
w=str(t).split()
s,q=0,''
if w[0][0]=='>':
q=w[0]+' '
w.pop(0)
for e in range(1,len(w)-1):
if w[e][-1:]=='.':w[e]+=' '
if len(q)+len(' '.join(w[s:e+1]))>=m:
#print n,q+' '.join(w[s:e])
n+=1; s=e
#print n,q+' '.join(w[s:len(w)])
def split_NEW(t,n,m):
w=str(t).split()
s,q,z=0,'',0
if w[0][0]=='>':
q=w[0]+' '
w.pop(0)
for e in range(1,len(w)-1):
if w[e][-1:]=='.':w[e]+=' '
for i in range(s,e+2):
z+=(len(w[i])+1)
if len(q)+z>m:
#print n,q+' '.join(w[s:e+1])
n+=1;s=e+1
z=0
#print n,q+' '.join(w[s:len(w)])
txt = "> Intel doesn't have to write a kernel from scratch. Nor does
Android. They can use Linux. And if they need to make modifications for
their own benefit, that's fine, just share that back. They benefited by
not having to develop from scratch. But they need to give something back
in return. Like the work they added. Both parties are give and take
something from each other. I'll take that over the BSD license any day
of the week."
loops = int(sys.argv[1])
n,b=1,60
startTime = time.clock()
for j in range(loops): split_ORIG(txt,n,b)
endTime = time.clock()
print "ORIG : %.2g seconds" % (endTime-startTime)
startTime = time.clock()
for j in range(loops): split_NEW(txt,n,b)
endTime = time.clock()
print "NEW : %.2g seconds" % (endTime-startTime)
----------------------------------------------------------------------
$ python splitlength.py 1000
ORIG : 0.19 seconds
NEW : 0.38 seconds
I told your dumb ass before: python list operations are slow.
Having to walk a list and check the size of each element is much slower
than joining the elements and checking the size of the join()ed string.
Got it, moron?
As you like to say: "Don't post unless you know EXACTLY what you're
talking about".
So to all you blabbermouths named Feeb Russell, we can only say:
FAHCK YOU!! FAHCK YOU!!
[toc] | [prev] | [next] | [standalone]
| From | deplorable owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-10-21 08:53 +0000 |
| Message-ID | <ahjgud092.agx3@rooftop.invalid> |
| In reply to | #376920 |
DFS <nospam@dfs.com> wrote:
> On 10/6/2016 4:00 PM, Adlbifhr Mjduhgfks wrote:
>
>
>> Furthermore, the dumb fuck is actually manipulating strings,
>> which always is a computationally very expensive undertaking.
>
>
> My original code executed the join() string operation once for each word
> in the input (78), plus once per line of screen output (8 more), for a
> total of 86 per run. Sounds like a lot.
>
> So I wrote a new routine that eliminated all but the 8 join() outputs to
> screen. It keeps a running total of the length of words (elements in
> the list), and when that total meets or exceeds the block size, it
> join()s the applicable elements and writes the line to screen.
>
> Basically:
> * original code join()s strings then evaluates length.
> * new code evaluates lengths of the strings then does join().
>
> The output of the two is identical.
>
> ----------------------------------------------------------------------
> import sys,time
>
> def split_ORIG(t,n,m):
> w=str(t).split()
> s,q=0,''
> if w[0][0]=='>':
> q=w[0]+' '
> w.pop(0)
> for e in range(1,len(w)-1):
> if w[e][-1:]=='.':w[e]+=' '
> if len(q)+len(' '.join(w[s:e+1]))>=m:
> #print n,q+' '.join(w[s:e])
> n+=1; s=e
> #print n,q+' '.join(w[s:len(w)])
>
>
> def split_NEW(t,n,m):
> w=str(t).split()
> s,q,z=0,'',0
> if w[0][0]=='>':
> q=w[0]+' '
> w.pop(0)
> for e in range(1,len(w)-1):
> if w[e][-1:]=='.':w[e]+=' '
> for i in range(s,e+2):
> z+=(len(w[i])+1)
> if len(q)+z>m:
> #print n,q+' '.join(w[s:e+1])
> n+=1;s=e+1
> z=0
> #print n,q+' '.join(w[s:len(w)])
>
>
>
> txt = "> Intel doesn't have to write a kernel from scratch. Nor does
> Android. They can use Linux. And if they need to make modifications for
> their own benefit, that's fine, just share that back. They benefited by
> not having to develop from scratch. But they need to give something back
> in return. Like the work they added. Both parties are give and take
> something from each other. I'll take that over the BSD license any day
> of the week."
>
> loops = int(sys.argv[1])
>
> n,b=1,60
>
> startTime = time.clock()
> for j in range(loops): split_ORIG(txt,n,b)
> endTime = time.clock()
> print "ORIG : %.2g seconds" % (endTime-startTime)
>
> startTime = time.clock()
> for j in range(loops): split_NEW(txt,n,b)
> endTime = time.clock()
> print "NEW : %.2g seconds" % (endTime-startTime)
> ----------------------------------------------------------------------
>
> $ python splitlength.py 1000
> ORIG : 0.19 seconds
> NEW : 0.38 seconds
>
>
> I told your dumb ass before: python list operations are slow.
>
> Having to walk a list and check the size of each element is much slower
> than joining the elements and checking the size of the join()ed string.
>
> Got it, moron?
>
> As you like to say: "Don't post unless you know EXACTLY what you're
> talking about".
>
> So to all you blabbermouths named Feeb Russell, we can only say:
>
> FAHCK YOU!! FAHCK YOU!!
>
python pwned by C.
anon@lowtide:~/code/blah$ rm out
anon@lowtide:~/code/blah$ time ./bah 15 40 1000 >out
real 0m0.018s
user 0m0.012s
sys 0m0.004s
anon@lowtide:~/code/blah$ wc -l out
13000 out
anon@lowtide:~/code/blah$ head -n 20 out
15 > Intel doesn't have to write a kernel from
16 > scratch. Nor does Android. They can use
17 > Linux. And if they need to make
18 > modifications for their own benefit,
19 > that's fine, just share that back. They
20 > benefited by not having to develop from
21 > scratch. But they need to give something
22 > back in return. Like the work they
23 > added. Both parties are give and take
24 > something from each other. I'll take
25 > that over the BSD license any day of the
26 > week.
15 > Intel doesn't have to write a kernel from
16 > scratch. Nor does Android. They can use
17 > Linux. And if they need to make
18 > modifications for their own benefit,
19 > that's fine, just share that back. They
20 > benefited by not having to develop from
21 > scratch. But they need to give something
anon@lowtide:~/code/blah$
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2016-10-21 13:19 +0200 |
| Message-ID | <20161021131946.6c5d8f56@maxa-pc.cpe.bvcom.net> |
| In reply to | #377114 |
On Fri, 21 Oct 2016 08:53:34 +0000 (UTC)
deplorable owl <owl@rooftop.invalid> wrote:
> DFS <nospam@dfs.com> wrote:
> > On 10/6/2016 4:00 PM, Adlbifhr Mjduhgfks wrote:
> >
> >
> >> Furthermore, the dumb fuck is actually manipulating strings,
> >> which always is a computationally very expensive undertaking.
> >
> >
> > My original code executed the join() string operation once for each
> > word in the input (78), plus once per line of screen output (8
> > more), for a total of 86 per run. Sounds like a lot.
> >
> > So I wrote a new routine that eliminated all but the 8 join()
> > outputs to screen. It keeps a running total of the length of words
> > (elements in the list), and when that total meets or exceeds the
> > block size, it join()s the applicable elements and writes the line
> > to screen.
> >
> > Basically:
> > * original code join()s strings then evaluates length.
> > * new code evaluates lengths of the strings then does join().
> >
> > The output of the two is identical.
> >
> > ----------------------------------------------------------------------
> > import sys,time
> >
> > def split_ORIG(t,n,m):
> > w=str(t).split()
> > s,q=0,''
> > if w[0][0]=='>':
> > q=w[0]+' '
> > w.pop(0)
> > for e in range(1,len(w)-1):
> > if w[e][-1:]=='.':w[e]+=' '
> > if len(q)+len(' '.join(w[s:e+1]))>=m:
> > #print n,q+' '.join(w[s:e])
> > n+=1; s=e
> > #print n,q+' '.join(w[s:len(w)])
> >
> >
> > def split_NEW(t,n,m):
> > w=str(t).split()
> > s,q,z=0,'',0
> > if w[0][0]=='>':
> > q=w[0]+' '
> > w.pop(0)
> > for e in range(1,len(w)-1):
> > if w[e][-1:]=='.':w[e]+=' '
> > for i in range(s,e+2):
> > z+=(len(w[i])+1)
> > if len(q)+z>m:
> > #print n,q+' '.join(w[s:e+1])
> > n+=1;s=e+1
> > z=0
> > #print n,q+' '.join(w[s:len(w)])
> >
> >
> >
> > txt = "> Intel doesn't have to write a kernel from scratch. Nor does
> > Android. They can use Linux. And if they need to make
> > modifications for their own benefit, that's fine, just share that
> > back. They benefited by not having to develop from scratch. But
> > they need to give something back in return. Like the work they
> > added. Both parties are give and take something from each other.
> > I'll take that over the BSD license any day of the week."
> >
> > loops = int(sys.argv[1])
> >
> > n,b=1,60
> >
> > startTime = time.clock()
> > for j in range(loops): split_ORIG(txt,n,b)
> > endTime = time.clock()
> > print "ORIG : %.2g seconds" % (endTime-startTime)
> >
> > startTime = time.clock()
> > for j in range(loops): split_NEW(txt,n,b)
> > endTime = time.clock()
> > print "NEW : %.2g seconds" % (endTime-startTime)
> > ----------------------------------------------------------------------
> >
> > $ python splitlength.py 1000
> > ORIG : 0.19 seconds
> > NEW : 0.38 seconds
> >
> >
> > I told your dumb ass before: python list operations are slow.
> >
> > Having to walk a list and check the size of each element is much
> > slower than joining the elements and checking the size of the
> > join()ed string.
> >
> > Got it, moron?
> >
> > As you like to say: "Don't post unless you know EXACTLY what you're
> > talking about".
> >
> > So to all you blabbermouths named Feeb Russell, we can only say:
> >
> > FAHCK YOU!! FAHCK YOU!!
> >
>
> python pwned by C.
> anon@lowtide:~/code/blah$ rm out
> anon@lowtide:~/code/blah$ time ./bah 15 40 1000 >out
>
> real 0m0.018s
> user 0m0.012s
> sys 0m0.004s
> anon@lowtide:~/code/blah$ wc -l out
> 13000 out
> anon@lowtide:~/code/blah$ head -n 20 out
> 15 > Intel doesn't have to write a kernel from
> 16 > scratch. Nor does Android. They can use
> 17 > Linux. And if they need to make
> 18 > modifications for their own benefit,
> 19 > that's fine, just share that back. They
> 20 > benefited by not having to develop from
> 21 > scratch. But they need to give something
> 22 > back in return. Like the work they
> 23 > added. Both parties are give and take
> 24 > something from each other. I'll take
> 25 > that over the BSD license any day of the
> 26 > week.
>
> 15 > Intel doesn't have to write a kernel from
> 16 > scratch. Nor does Android. They can use
> 17 > Linux. And if they need to make
> 18 > modifications for their own benefit,
> 19 > that's fine, just share that back. They
> 20 > benefited by not having to develop from
> 21 > scratch. But they need to give something
> anon@lowtide:~/code/blah$
>
[bmaxa@maxa-pc haskell]$ time ./split_line 15 40 1000 > out.txt
real 0m0.036s
user 0m0.033s
sys 0m0.000s
[bmaxa@maxa-pc haskell]$ wc -l out.txt
13000 out.txt
[bmaxa@maxa-pc haskell]$ head -n 20 out.txt
15 > Intel doesn't have to write a kernel
16 > from scratch. Nor does Android. They
17 > can use Linux. And if they need to make
18 > modifications for their own benefit,
19 > that's fine, just share that back. They
20 > benefited by not having to develop from
21 > scratch. But they need to give
22 > something back in return. Like the work
23 > they added. Both parties are give and
24 > take something from each other. I'll
25 > take that over the BSD license any day
26 > of the week.
15 > Intel doesn't have to write a kernel
16 > from scratch. Nor does Android. They
17 > can use Linux. And if they need to make
18 > modifications for their own benefit,
19 > that's fine, just share that back. They
20 > benefited by not having to develop from
21 > scratch. But they need to give
[bmaxa@maxa-pc haskell]$ cat split_line.hs
import System.Environment
import Control.Monad
reformat (x:xs) enum len = if x == '>'
then reformat' (words xs) [] [] enum
else reformat' (words (x:xs)) [] [] enum
where reformat' [] line lines i = unlines (lines ++ form i line)
reformat' (x:xs) line lines i = if length (unwords (x:line)) < len
then reformat' xs (x:line) lines i
else reformat'
(x:xs) []
(lines++form i line)
(i+1)
form i line = [show i ++ " > " ++ unwords (reverse line)]
main = do
args <- getArgs
let (enum:len:count:_) = map read args
replicateM count (putStrLn $ reformat txt enum len)
txt = "> Intel doesn't have to write a kernel from scratch. Nor does\
\ Android. They can use Linux. And if they need to make modifications for\
\ their own benefit, that's fine, just share that back. They benefited by\
\ not having to develop from scratch. But they need to give something back\
\ in return. Like the work they added. Both parties are give and take\
\ something from each other. I'll take that over the BSD license any day\
\ of the week."
--
press any key to continue or any other to quit
[toc] | [prev] | [next] | [standalone]
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web