Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #172150 > unrolled thread
| Started by | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| First post | 2023-08-13 06:42 -0700 |
| Last post | 2023-08-14 21:14 +0000 |
| Articles | 20 on this page of 102 — 27 participants |
Back to article view | Back to comp.lang.c
Piping to stdin Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 06:42 -0700
Re: Piping to stdin Spiros Bousbouras <spibou@gmail.com> - 2023-08-13 13:55 +0000
Re: Piping to stdin Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 07:07 -0700
Re: Piping to stdin Bart <bc@freeuk.com> - 2023-08-13 15:21 +0100
Re: Piping to stdin Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 07:31 -0700
Re: Piping to stdin Bart <bc@freeuk.com> - 2023-08-13 16:40 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 16:08 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 16:07 +0000
Re: Piping to stdin Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-13 17:26 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-13 19:09 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 20:45 +0000
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-13 20:53 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 20:47 +0000
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 00:59 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 03:07 +0000
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 03:12 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-14 15:14 +0000
Re: Piping to stdin "Gary R. Schmidt" <grschmidt@acm.org> - 2023-08-15 12:50 +1000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 04:59 +0000
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-14 23:15 -0700
Re: Piping to stdin Richard Kettlewell <invalid@invalid.invalid> - 2023-08-15 08:50 +0100
Dealing with weird filenames (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-15 08:10 +0000
Re: Piping to stdin David Brown <david.brown@hesbynett.no> - 2023-08-15 15:34 +0200
Re: Piping to stdin Richard Harnden <richard.nospam@gmail.com> - 2023-08-15 19:50 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 20:16 +0000
Re: Piping to stdin vallor <vallor@cultnix.org> - 2023-08-16 06:34 +0000
Re: Piping to stdin Richard Kettlewell <invalid@invalid.invalid> - 2023-08-16 17:39 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-16 17:37 +0000
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-16 17:43 +0000
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-16 13:35 -0700
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-17 14:51 +0300
Re: Piping to stdin James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-08-16 01:37 -0400
Re: Piping to stdin David Brown <david.brown@hesbynett.no> - 2023-08-16 13:14 +0200
Re: Piping to stdin Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-08-15 12:08 -0600
Re: Piping to stdin Richard Harnden <richard.nospam@gmail.com> - 2023-08-16 09:32 +0100
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-16 17:27 +0300
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-15 14:30 +0000
Re: Piping to stdin Giovanni <lsodgf0@home.net.it> - 2023-08-15 17:14 +0200
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-15 15:48 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-15 16:12 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-15 16:15 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-15 16:22 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 10:26 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-17 14:23 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-17 15:25 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 17:33 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 23:32 +0300
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 10:32 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-17 14:57 +0300
Re: Piping to stdin Michael S <already5chosen@yahoo.com> - 2023-08-17 05:14 -0700
Wrecking a good thing? (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-17 14:09 +0000
Re: Wrecking a good thing? Phil Carmody <pc+usenet@asdf.org> - 2023-08-18 00:39 +0300
Re: Wrecking a good thing? (Was: Piping to stdin) David Brown <david.brown@hesbynett.no> - 2023-08-18 11:17 +0200
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 15:14 +0000
Re: Piping to stdin Öö Tiib <ootiib@hot.ee> - 2023-08-17 08:58 -0700
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-17 13:52 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 15:20 +0000
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-17 13:43 -0700
Re: Piping to stdin David Brown <david.brown@hesbynett.no> - 2023-08-18 11:28 +0200
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-17 21:52 +0100
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-19 13:33 +0300
Re: Piping to stdin Oğuz <oguzismailuysal@gmail.com> - 2023-08-19 16:15 +0300
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-19 14:48 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-20 17:24 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-20 19:21 +0000
Re: Piping to stdin Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-20 21:57 +0100
What language is this? (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-20 22:33 +0000
Re: What language is this? (Was: Piping to stdin) scott@slp53.sl.home (Scott Lurndal) - 2023-08-21 01:26 +0000
Re: What language is this? (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-21 02:57 +0000
Re: What language is this? Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-21 17:16 +0100
Re: What language is this? gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-21 19:10 +0000
Re: What language is this? Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-21 20:31 +0100
Re: What language is this? gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-21 20:29 +0000
Re: What language is this? Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-21 21:48 +0100
Re: What language is this? (Was: Piping to stdin) Muttley@dastardlyhq.com - 2023-08-21 06:50 +0000
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-19 21:14 +0100
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 23:24 +0300
Re: Piping to stdin Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-15 20:50 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-16 17:11 +0300
Re: Piping to stdin Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-16 15:25 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-16 19:29 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-17 14:49 +0300
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-16 03:20 +0100
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 18:33 +0300
Re: Piping to stdin "Nuno Silva" <nunojsilva@invalid.invalid> - 2023-08-14 09:45 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 16:06 +0000
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-13 17:09 -0700
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 01:03 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 04:00 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-14 12:20 +0300
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-14 02:44 -0700
Re: Piping to stdin Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-14 03:54 -0700
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 11:22 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 15:49 +0000
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-14 17:19 +0100
Re: Piping to stdin Jim Jackson <jj@franjam.org.uk> - 2023-08-14 17:21 +0000
Re: Piping to stdin Michael S <already5chosen@yahoo.com> - 2023-08-15 08:02 -0700
Re: Piping to stdin John Forkosh <forkosh@panix.com> - 2023-08-14 03:15 +0000
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 11:28 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 15:41 +0000
Re: Piping to stdin Richard Harnden <richard.nospam@gmail.com> - 2023-08-14 22:02 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 21:14 +0000
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
| From | Phil Carmody <pc+usenet@asdf.org> |
|---|---|
| Date | 2023-08-19 13:33 +0300 |
| Message-ID | <87wmxr9v9l.fsf@fatphil.org> |
| In reply to | #172478 |
Ben Bacarisse <ben.usenet@bsb.me.uk> writes: > Some file systems (depending on mount options) can have complex rules > such as rejecting any name with an invalid UTF-8 sequence. Oooh, now I'm tempted to name files in Latin-1, to deliberately break filesystems that make such assumptions! Phil -- We are no longer hunters and nomads. No longer awed and frightened, as we have gained some understanding of the world in which we live. As such, we can cast aside childish remnants from the dawn of our civilization. -- NotSanguine on SoylentNews, after Eugen Weber in /The Western Tradition/
[toc] | [prev] | [next] | [standalone]
| From | Oğuz <oguzismailuysal@gmail.com> |
|---|---|
| Date | 2023-08-19 16:15 +0300 |
| Message-ID | <ubqf9k$r2ol$1@dont-email.me> |
| In reply to | #172520 |
On 8/19/23 1:33 PM, Phil Carmody wrote: > Ben Bacarisse <ben.usenet@bsb.me.uk> writes: >> Some file systems (depending on mount options) can have complex rules >> such as rejecting any name with an invalid UTF-8 sequence. > > Oooh, now I'm tempted to name files in Latin-1, to deliberately break > filesystems that make such assumptions! Be careful with that attitude. The "memory-safe" sudo replacement doesn't support non-UTF-8 input either: https://github.com/memorysafety/sudo-rs/issues/213
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2023-08-19 14:48 +0000 |
| Message-ID | <ubqkn7$skrr$1@dont-email.me> |
| In reply to | #172532 |
On Sat, 19 Aug 2023 16:15:32 +0300 =?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com> wrote: >On 8/19/23 1:33 PM, Phil Carmody wrote: >> Ben Bacarisse <ben.usenet@bsb.me.uk> writes: >>> Some file systems (depending on mount options) can have complex rules >>> such as rejecting any name with an invalid UTF-8 sequence. >> >> Oooh, now I'm tempted to name files in Latin-1, to deliberately break >> filesystems that make such assumptions! >Be careful with that attitude. The "memory-safe" sudo replacement >doesn't support non-UTF-8 input either: Whats memory unsafe about sudo?
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2023-08-20 17:24 +0000 |
| Message-ID | <y%rEM.716067$AsA.587368@fx18.iad> |
| In reply to | #172537 |
Muttley@dastardlyhq.com writes: >On Sat, 19 Aug 2023 16:15:32 +0300 >=?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com> wrote: >>On 8/19/23 1:33 PM, Phil Carmody wrote: >>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes: >>>> Some file systems (depending on mount options) can have complex rules >>>> such as rejecting any name with an invalid UTF-8 sequence. >>> >>> Oooh, now I'm tempted to name files in Latin-1, to deliberately break >>> filesystems that make such assumptions! >>Be careful with that attitude. The "memory-safe" sudo replacement >>doesn't support non-UTF-8 input either: > >Whats memory unsafe about sudo? > https://www.cisa.gov/news-events/alerts/2021/02/02/sudo-heap-based-buffer-overflow-vulnerability-cve-2021-3156
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2023-08-20 19:21 +0000 |
| Message-ID | <ubtp4d$1gqlu$1@dont-email.me> |
| In reply to | #172591 |
On Sun, 20 Aug 2023 17:24:46 GMT scott@slp53.sl.home (Scott Lurndal) wrote: >Muttley@dastardlyhq.com writes: >>On Sat, 19 Aug 2023 16:15:32 +0300 >>=?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com> wrote: >>>On 8/19/23 1:33 PM, Phil Carmody wrote: >>>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes: >>>>> Some file systems (depending on mount options) can have complex rules >>>>> such as rejecting any name with an invalid UTF-8 sequence. >>>> >>>> Oooh, now I'm tempted to name files in Latin-1, to deliberately break >>>> filesystems that make such assumptions! >>>Be careful with that attitude. The "memory-safe" sudo replacement >>>doesn't support non-UTF-8 input either: >> >>Whats memory unsafe about sudo? >> >https://www.cisa.gov/news-events/alerts/2021/02/02/sudo-heap-based-buffer-overf >low-vulnerability-cve-2021-3156 One bug in one version doesn't make it generally unsafe.
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2023-08-20 21:57 +0100 |
| Message-ID | <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #172537 |
Muttley@dastardlyhq.com writes: > On Sat, 19 Aug 2023 16:15:32 +0300 > =?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com> wrote: >>On 8/19/23 1:33 PM, Phil Carmody wrote: >>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes: >>>> Some file systems (depending on mount options) can have complex rules >>>> such as rejecting any name with an invalid UTF-8 sequence. >>> >>> Oooh, now I'm tempted to name files in Latin-1, to deliberately break >>> filesystems that make such assumptions! >>Be careful with that attitude. The "memory-safe" sudo replacement >>doesn't support non-UTF-8 input either: > > Whats memory unsafe about sudo? It's not written in a language whose extremely complicate runtime system that's conjectured to be bug free in this respect by Really Wishful Thinking[tm] is supposed to prevent simple memory access errors C supports.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2023-08-20 22:33 +0000 |
| Subject | What language is this? (Was: Piping to stdin) |
| Message-ID | <ubu4cd$3qqvc$1@news.xmission.com> |
| In reply to | #172599 |
In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>, Rainer Weikusat <rweikusat@talktalk.net> wrote: ... >It's not written in a language whose extremely complicate runtime >system that's conjectured to be bug free in this respect by Really >Wishful Thinking[tm] is supposed to prevent simple memory access errors >C supports. What language was this quoted paragraph written in? Preumably one in which word order doesn't matter. -- The randomly chosen signature file that would have appeared here is more than 4 lines long. As such, it violates one or more Usenet RFCs. In order to remain in compliance with said RFCs, the actual sig can be found at the following URL: http://user.xmission.com/~gazelle/Sigs/Reaganomics
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2023-08-21 01:26 +0000 |
| Subject | Re: What language is this? (Was: Piping to stdin) |
| Message-ID | <g3zEM.718458$AsA.196497@fx18.iad> |
| In reply to | #172602 |
gazelle@shell.xmission.com (Kenny McCormack) writes: >In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>, >Rainer Weikusat <rweikusat@talktalk.net> wrote: >... >>It's not written in a language whose extremely complicate runtime >>system that's conjectured to be bug free in this respect by Really >>Wishful Thinking[tm] is supposed to prevent simple memory access errors >>C supports. > >What language was this quoted paragraph written in? > >Preumably one in which word order doesn't matter. Word order in German and English don't always agree. Basically he is saying, somewhat mockingly, that because it is not written in Rust, sudo written in C is inherently memory unsafe.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2023-08-21 02:57 +0000 |
| Subject | Re: What language is this? (Was: Piping to stdin) |
| Message-ID | <ubujqh$3r3b4$1@news.xmission.com> |
| In reply to | #172608 |
In article <g3zEM.718458$AsA.196497@fx18.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
>gazelle@shell.xmission.com (Kenny McCormack) writes:
>>In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>,
>>Rainer Weikusat <rweikusat@talktalk.net> wrote:
>>...
>>>It's not written in a language whose extremely complicate runtime
>>>system that's conjectured to be bug free in this respect by Really
>>>Wishful Thinking[tm] is supposed to prevent simple memory access errors
>>>C supports.
>>
>>What language was this quoted paragraph written in?
>>
>>Preumably one in which word order doesn't matter.
>
>Word order in German and English don't always agree.
>
>Basically he is saying, somewhat mockingly, that because it is
>not written in Rust, sudo written in C is inherently memory unsafe.
OK, thanks.
I am glad that you were able to intuit that "Rust" was "the other language"
involved in the comparison.
--
They say compassion is a virtue, but I don't have the time!
- David Byrne -
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2023-08-21 17:16 +0100 |
| Subject | Re: What language is this? |
| Message-ID | <87v8d8jrpo.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #172612 |
gazelle@shell.xmission.com (Kenny McCormack) writes: > In article <g3zEM.718458$AsA.196497@fx18.iad>, > Scott Lurndal <slp53@pacbell.net> wrote: >>gazelle@shell.xmission.com (Kenny McCormack) writes: >>>In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>, >>>Rainer Weikusat <rweikusat@talktalk.net> wrote: >>>... >>>>It's not written in a language whose extremely complicate runtime >>>>system that's conjectured to be bug free in this respect by Really >>>>Wishful Thinking[tm] is supposed to prevent simple memory access errors >>>>C supports. >>> >>>What language was this quoted paragraph written in? >>> >>>Preumably one in which word order doesn't matter. >> >>Word order in German and English don't always agree. >> >>Basically he is saying, somewhat mockingly, that because it is >>not written in Rust, sudo written in C is inherently memory unsafe. > > OK, thanks. > > I am glad that you were able to intuit that "Rust" was "the other language" > involved in the comparison. That's pretty obvious from the ,---- | Be careful with that attitude. The "memory-safe" sudo replacement | doesn't support non-UTF-8 input either: | | https://github.com/memorysafety/sudo-rs/issues/213 `---- upthread. Rust is conjectured to be memory safe because people using it really want to believe that the Rust runtime - some orders of magnitude more complicated than a real lot of C programs - has not such bugs.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2023-08-21 19:10 +0000 |
| Subject | Re: What language is this? |
| Message-ID | <uc0cqr$3rv8t$2@news.xmission.com> |
| In reply to | #172630 |
In article <87v8d8jrpo.fsf@doppelsaurus.mobileactivedefense.com>, Rainer Weikusat <rweikusat@talktalk.net> wrote: ... >,---- >| Be careful with that attitude. The "memory-safe" sudo replacement >| doesn't support non-UTF-8 input either: >| >| https://github.com/memorysafety/sudo-rs/issues/213 >`---- That URL means nothing to me. But that's just me. Don't take it personally. -- The randomly chosen signature file that would have appeared here is more than 4 lines long. As such, it violates one or more Usenet RFCs. In order to remain in compliance with said RFCs, the actual sig can be found at the following URL: http://user.xmission.com/~gazelle/Sigs/Seriously
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2023-08-21 20:31 +0100 |
| Subject | Re: What language is this? |
| Message-ID | <87r0nwjios.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #172633 |
gazelle@shell.xmission.com (Kenny McCormack) writes: > In article <87v8d8jrpo.fsf@doppelsaurus.mobileactivedefense.com>, > Rainer Weikusat <rweikusat@talktalk.net> wrote: > ... >>,---- >>| Be careful with that attitude. The "memory-safe" sudo replacement >>| doesn't support non-UTF-8 input either: >>| >>| https://github.com/memorysafety/sudo-rs/issues/213 >>`---- > > That URL means nothing to me. But that's just me. Don't take it > personally. In this case, I suggest one of two options 1) You'll try to memorize that rs commonly means Rust. Eg, it's usually the extension used for Rust source files. 2) You'll ask your full-time carer to click on the link for you and read the content of the page to you. In either case, posting more lame flames into this groups for no conceivable reason is not going to improve your understanding of anything.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2023-08-21 20:29 +0000 |
| Subject | Re: What language is this? |
| Message-ID | <uc0hft$3s1du$1@news.xmission.com> |
| In reply to | #172635 |
In article <87r0nwjios.fsf@doppelsaurus.mobileactivedefense.com>, Rainer Weikusat <rweikusat@talktalk.net> wrote: >blah, blah, blah I told you not to take it personally, but what do you go and do? All I can say is that I tried to help you and to steer you in the right direction. -- Men rarely (if ever) manage to dream up a God superior to themselves. Most Gods have the manners and morals of a spoiled child.
[toc] | [prev] | [next] | [standalone]
| From | Rainer Weikusat <rweikusat@talktalk.net> |
|---|---|
| Date | 2023-08-21 21:48 +0100 |
| Subject | Re: What language is this? |
| Message-ID | <87msykjf4p.fsf@doppelsaurus.mobileactivedefense.com> |
| In reply to | #172636 |
gazelle@shell.xmission.com (Kenny McCormack) writes: > In article <87r0nwjios.fsf@doppelsaurus.mobileactivedefense.com>, > Rainer Weikusat <rweikusat@talktalk.net> wrote: >>blah, blah, blah > > I told you not to take it personally, but what do you go and do? I'm principally interested in technical discussions, eg, about Rust and memory safety, and sometimes motivated to try my hands at minimally creative flames when people are trying to play the Most Importinant Dickhead with the help of the usual boilerplate phrases.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2023-08-21 06:50 +0000 |
| Subject | Re: What language is this? (Was: Piping to stdin) |
| Message-ID | <ubv1er$1pvkr$1@dont-email.me> |
| In reply to | #172608 |
On Mon, 21 Aug 2023 01:26:36 GMT scott@slp53.sl.home (Scott Lurndal) wrote: >gazelle@shell.xmission.com (Kenny McCormack) writes: >>In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>, >>Rainer Weikusat <rweikusat@talktalk.net> wrote: >>... >>>It's not written in a language whose extremely complicate runtime >>>system that's conjectured to be bug free in this respect by Really >>>Wishful Thinking[tm] is supposed to prevent simple memory access errors >>>C supports. >> >>What language was this quoted paragraph written in? >> >>Preumably one in which word order doesn't matter. > >Word order in German and English don't always agree. > >Basically he is saying, somewhat mockingly, that because it is >not written in Rust, sudo written in C is inherently memory unsafe. To do anything low level Rust has to disable memory protection (or whatever they call it) anyway, so its no safer than C/C++ in these circumstances.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2023-08-19 21:14 +0100 |
| Message-ID | <87v8davlg1.fsf@bsb.me.uk> |
| In reply to | #172520 |
Phil Carmody <pc+usenet@asdf.org> writes: > Ben Bacarisse <ben.usenet@bsb.me.uk> writes: >> Some file systems (depending on mount options) can have complex rules >> such as rejecting any name with an invalid UTF-8 sequence. > > Oooh, now I'm tempted to name files in Latin-1, to deliberately break > filesystems that make such assumptions! Why? -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Phil Carmody <pc+usenet@asdf.org> |
|---|---|
| Date | 2023-08-15 23:24 +0300 |
| Message-ID | <87sf8k2gw3.fsf@fatphil.org> |
| In reply to | #172311 |
kalevi@kolttonen.fi (Kalevi Kolttonen) writes: > Kenny McCormack <gazelle@shell.xmission.com> wrote: >> But do they know that??? > > "They" probably don't know it. But let's face it, > nobody really wants to create a file having '-' > filename on purpose. The filename is not descriptive > at all, it would be just an insane choice for anything > useful. > > It could happen by accident, but even that is quite > unlikely. > > If "they" don't know how to delete it, there is no need > to panic. The file's existence does no harm. "They" can > always ask for help and someone will tell them how > to get rid of it. > > I guess the stdin convention '-' is decades old. > It was chosen because they had pick something that > is short and not likely to exist as a real file. I propose that '|' might have been better - it's even mnemonic. Phil -- We are no longer hunters and nomads. No longer awed and frightened, as we have gained some understanding of the world in which we live. As such, we can cast aside childish remnants from the dawn of our civilization. -- NotSanguine on SoylentNews, after Eugen Weber in /The Western Tradition/
[toc] | [prev] | [next] | [standalone]
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Date | 2023-08-15 20:50 +0000 |
| Message-ID | <ubgoee$2rs7p$1@dont-email.me> |
| In reply to | #172331 |
On Tue, 15 Aug 2023 23:24:28 +0300, Phil Carmody wrote: > kalevi@kolttonen.fi (Kalevi Kolttonen) writes: >> Kenny McCormack <gazelle@shell.xmission.com> wrote: >>> But do they know that??? >> >> "They" probably don't know it. But let's face it, >> nobody really wants to create a file having '-' >> filename on purpose. The filename is not descriptive >> at all, it would be just an insane choice for anything >> useful. >> >> It could happen by accident, but even that is quite >> unlikely. >> >> If "they" don't know how to delete it, there is no need >> to panic. The file's existence does no harm. "They" can >> always ask for help and someone will tell them how >> to get rid of it. >> >> I guess the stdin convention '-' is decades old. >> It was chosen because they had pick something that >> is short and not likely to exist as a real file. > > I propose that '|' might have been better - it's even mnemonic. But, '|' conflicts with the shell pipe character, and would need a workaround in some cases. For example, foo bar | blech could either pipe stdout from foo (which processed bar) into blech, or it could instruct foo to accept bar, stdin and blech as inputs. And, unless you escape or singlequote the pipe character, the pipe-command interpretation wins. Similarly, foo bar - blech could either ask foo to read files "bar", "-" and "blech" /or/ ask foo to read files "bar", stdin, and "blech", depending on the presence (or absence) of a file named "-" Again, the accepted method of discerning one from the other is to modify that "-" to "./-", indicating a file (in the current working directory) named "-". So, pOHtato, pAHtato. -- Lew Pitcher "In Skills We Trust"
[toc] | [prev] | [next] | [standalone]
| From | Phil Carmody <pc+usenet@asdf.org> |
|---|---|
| Date | 2023-08-16 17:11 +0300 |
| Message-ID | <87fs4j2i27.fsf@fatphil.org> |
| In reply to | #172336 |
Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes: > On Tue, 15 Aug 2023 23:24:28 +0300, Phil Carmody wrote: >> kalevi@kolttonen.fi (Kalevi Kolttonen) writes: >>> Kenny McCormack <gazelle@shell.xmission.com> wrote: >>>> But do they know that??? >>> >>> "They" probably don't know it. But let's face it, >>> nobody really wants to create a file having '-' >>> filename on purpose. The filename is not descriptive >>> at all, it would be just an insane choice for anything >>> useful. >>> >>> It could happen by accident, but even that is quite >>> unlikely. >>> >>> If "they" don't know how to delete it, there is no need >>> to panic. The file's existence does no harm. "They" can >>> always ask for help and someone will tell them how >>> to get rid of it. >>> >>> I guess the stdin convention '-' is decades old. >>> It was chosen because they had pick something that >>> is short and not likely to exist as a real file. >> >> I propose that '|' might have been better - it's even mnemonic. > > But, '|' conflicts with the shell pipe character, and would need > a workaround in some cases. For example, It's doing something special, why wouldn't you expect to do something special to make use of it? Phil -- We are no longer hunters and nomads. No longer awed and frightened, as we have gained some understanding of the world in which we live. As such, we can cast aside childish remnants from the dawn of our civilization. -- NotSanguine on SoylentNews, after Eugen Weber in /The Western Tradition/
[toc] | [prev] | [next] | [standalone]
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Date | 2023-08-16 15:25 +0000 |
| Message-ID | <ubipom$3ajkp$1@dont-email.me> |
| In reply to | #172377 |
On Wed, 16 Aug 2023 17:11:28 +0300, Phil Carmody wrote: > Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes: >> On Tue, 15 Aug 2023 23:24:28 +0300, Phil Carmody wrote: [snip] >>>> I guess the stdin convention '-' is decades old. >>>> It was chosen because they had pick something that >>>> is short and not likely to exist as a real file. >>> >>> I propose that '|' might have been better - it's even mnemonic. >> >> But, '|' conflicts with the shell pipe character, and would need >> a workaround in some cases. For example, > > It's doing something special, why wouldn't you expect to do something > special to make use of it? Okay, then. How about a counter proposal: For Unix shells, the < character indicates redirection of stdin. I propose that '<' might have been a better choice as a standard program option to flag "read from stdin" than either '|' /or/ '-' were. :-) -- Lew Pitcher "In Skills We Trust"
[toc] | [prev] | [next] | [standalone]
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
Back to top | Article view | comp.lang.c
csiph-web