Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #89895 > unrolled thread
| Started by | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| First post | 2026-08-14 12:26 +0100 |
| Last post | 2026-08-17 20:27 +0100 |
| Articles | 9 on this page of 89 — 13 participants |
Back to article view | Back to comp.os.linux.misc
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Manipulating C code at the AST level, in C Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-14 12:26 +0100
Re: Manipulating C code at the AST level, in C Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2026-08-14 13:53 +0100
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-14 21:10 +0000
Re: Manipulating C code at the AST level, in C scott@slp53.sl.home (Scott Lurndal) - 2026-08-14 16:00 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-14 23:47 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-15 07:20 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-15 11:33 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-15 22:41 -0400
Re: Manipulating C code at the AST level, in C "Carlos E. R." <robin_listas@es.invalid> - 2026-08-16 10:50 +0200
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-16 19:04 +0000
Re: Manipulating C code at the AST level, in C Jim Jackson <jj@franjam.org.uk> - 2026-08-15 11:07 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-15 12:18 +0100
Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-15 12:20 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-16 02:09 -0400
Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-16 09:59 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-16 11:42 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-17 00:02 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-17 07:10 +0000
Re: Manipulating C code at the AST level, in C Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-17 09:32 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-17 10:13 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-17 17:15 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-17 20:58 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-17 22:24 -0400
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-18 04:55 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-18 06:17 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-18 22:11 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 04:21 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-19 02:26 -0400
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:29 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:36 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:28 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:24 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-18 10:19 +0100
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-18 16:30 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 04:11 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 04:22 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-19 04:38 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 05:34 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 06:39 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-19 07:04 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:59 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 01:31 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 03:26 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 11:50 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 12:06 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-20 12:51 -0400
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-21 13:34 +0100
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-20 04:02 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 06:35 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:31 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:47 +0000
[off-topic] MA 370 flight disappearance (Was: Re: Manipulating C code at the AST level, in C) Anton Antimo <anton@safunu.org> - 2026-08-20 10:04 -0300
Re: [off-topic] MA 370 flight disappearance (Was: Re: Manipulating C code at the AST level, in C) rbowman <bowman@montana.com> - 2026-08-20 21:11 +0000
Re: [off-topic] MA 370 flight disappearance The Natural Philosopher <tnp@invalid.invalid> - 2026-08-21 13:32 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-19 02:28 -0400
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 16:57 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 22:17 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 01:34 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 03:45 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-19 23:26 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 21:40 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-20 23:42 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-21 06:10 +0000
Re: Manipulating C code at the AST level, in C Lars Poulsen <lars@beagle-ears.com> - 2026-08-21 06:01 -0700
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-21 18:36 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-21 21:46 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 06:30 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:15 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:39 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 22:54 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 04:03 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 01:25 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 03:56 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-20 04:40 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-20 04:46 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-20 04:59 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 21:46 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-20 22:44 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-21 04:35 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-21 00:54 -0400
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-21 00:05 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-16 19:13 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-17 01:14 -0400
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-17 16:58 +0000
Re: Manipulating C code at the AST level, in C Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2026-08-17 13:44 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-17 15:31 +0100
Re: Manipulating C code at the AST level, in C Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2026-08-18 13:23 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-18 17:16 +0100
Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-17 20:27 +0100
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-08-21 00:05 -0400 |
| Message-ID | <D9icnYFj4rVjUxr3nZ2dnZfqn_adnZ2d@giganews.com> |
| In reply to | #90243 |
On 8/20/26 17:46, rbowman wrote: > On Thu, 20 Aug 2026 04:40:36 GMT, Charlie Gibbs wrote: > >> Marijuana, hashish, mescaline, scopolamine Belladonna, cocaine, >> chloral hydrate, ephedrine Psilocybin, atropine, cannabis, >> amphetamine LBJ, LSD, MDA and DMT Do you know what you're doing? >> -- Terry Bush > > "The sporting editors had also given me $300 in cash, most of which was > already spent on extremely dangerous drugs. SEX And DRUGS and ROCK-n-ROLL !!! And, amazingly, almost everybody SURVIVED the 60s/70s :-) Guy laid some good blotter on me at about age 10 or maybe 11. Lucky I split it, but NOT disappointed :-) Later, the Natives know about some WEIRD shit found under rocks. Rad experience. Rad environments, 14000 foot mountain in a thunderstorm, you see "The Gods". Thought it was funny. Sorry, just not much into "theisms".
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-08-16 19:13 +0000 |
| Message-ID | <neegerFpk4lU15@mid.individual.net> |
| In reply to | #89923 |
On Sun, 16 Aug 2026 02:09:57 -0400, c186282 wrote: > You brought a > jacket so you could do shit in the CPU room. At RPI the shrine where the 360/30 lived was the only place on campus with A/C. Not a bad thing on those days when the humidity in the Hudson Valley hits 99.9%. The last place I worked was a converted mill building. Rather nice architecturally but every HVAC company in town had taken a shot at it with limited success. Programming wore flannel shirts in August and it wasn't a style thing. Portable electric heaters appeared to the consternation of the maintenance people. Conversely, I leaned toward short sleeved shirts in December. The poor bastards on the 2nd floor were on the opposite schedule.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-08-17 01:14 -0400 |
| Message-ID | <HqmcnefSxvKQBB_3nZ2dnZfqn_oAAAAA@giganews.com> |
| In reply to | #89945 |
On 8/16/26 15:13, rbowman wrote: > On Sun, 16 Aug 2026 02:09:57 -0400, c186282 wrote: > >> You brought a >> jacket so you could do shit in the CPU room. > > At RPI the shrine where the 360/30 lived was the only place on campus with > A/C. Not a bad thing on those days when the humidity in the Hudson Valley > hits 99.9%. Heh heh ... yea, there WAS a little span where the coolest place in town, literally, was the govt/biz CPU room ! > The last place I worked was a converted mill building. Rather nice > architecturally but every HVAC company in town had taken a shot at it with > limited success. Programming wore flannel shirts in August and it wasn't a > style thing. Portable electric heaters appeared to the consternation of > the maintenance people. Older buildings, like old British castles, were NOT designed with modern conveniences in mind. The Brits just ran lots of pipes and shit along the upper walls. Kinda ugly, but WORK. > Conversely, I leaned toward short sleeved shirts in December. The poor > bastards on the 2nd floor were on the opposite schedule. The old boxes had to be kept within a narrow temperature range. Mostly that's be 'cooler' but in winter might be 'hotter'. I remember an old govt place - a DEC cpu box, about a cubic meter, discrete transistors - in the middle of the room and all the tape drive units along the walls. They kept it about 55/60F in there at all times WITH an enforced breeze. BUT ... it supported dozens of serial terminals, local and remote, and everybody COULD get their necessary shit done. Almost *all* COBOL. Hmmm ... these days you can earn BIG money if you know, and can fix/mod, COBOL code from the 1960s. Rather a LOT of places paid BIG $$$ to have COBOL pros write their core operating software back then - and can now not AFFORD to port it all over to anything else. Oh, that olde-tyme COBOL code - SOLID ! Yer stereotypical white-shirt/narrow-tie guys who KNEW THEIR SHIT far better than most today. Not EVER gonna cuss them.
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2026-08-17 16:58 +0000 |
| Message-ID | <h5HgS.20567$X0O7.12952@fx35.iad> |
| In reply to | #89957 |
On 2026-08-17, c186282 <c186282@nnada.net> wrote: > The old boxes had to be kept within a narrow > temperature range. Mostly that's be 'cooler' > but in winter might be 'hotter'. Not as narrow as many people thought. I used to get into "thermostat wars" with people who believed that the purpose of air conditioning was not to make things comfortable - for people or machines - but to make things COLD. As with anything else a moderate approach worked quite well - but most people just couldn't stand the thought of a machine room being comfortable, so after I left they'd crank the thermostat right back down again. Most installations I worked in only ran the machines during office hours, shutting them down at the end of the day. One Friday evening I shut down the machine but forgot to shut off the air conditioning before leaving. Monday morning our breath was condensing in the machine room. The oil in the disk drives' hydraulic actuators congealed, and the heads wouldn't load until we left the disks spinning for the couple of hours it took for the oil to warm up. At another such shop, the machine was notoriously flaky. When the CE pulled one of the main boards out of the CPU, a VLSI chip fell out. The constant thermal cycling had caused the chips to literally walk out of their sockets. Once we left the machine on 24/7, the problems went away. -- /~\ Charlie Gibbs | In this world there are \ / <cgibbs@kltpzyxm.invalid> | two kinds of people: X I'm really at ac.dekanfrus | 1. Those who can extrapolate / \ if you read it the right way. | from incomplete data.
[toc] | [prev] | [next] | [standalone]
| From | Geoff Clare <geoff@clare.See-My-Signature.invalid> |
|---|---|
| Date | 2026-08-17 13:44 +0100 |
| Message-ID | <r9cblm-hl2.ln1@ID-313840.user.individual.net> |
| In reply to | #89909 |
Richard Kettlewell wrote:
> poll() doesn’t poll, despite the name.
Yes it does, if you tell it to.
Quoting from the SUS at the previously-given URL:
To effect a poll, the application shall ensure that the timeout
argument for poll() is 0, or for ppoll() is not a null pointer and
points to a zero-valued timespec structure.
--
Geoff Clare <netnews@gclare.org.uk>
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2026-08-17 15:31 +0100 |
| Message-ID | <115v5v9$12blk$2@dont-email.me> |
| In reply to | #89966 |
On 17/08/2026 13:44, Geoff Clare wrote: > Richard Kettlewell wrote: > >> poll() doesn’t poll, despite the name. > > Yes it does, if you tell it to. > > Quoting from the SUS at the previously-given URL: > > To effect a poll, the application shall ensure that the timeout > argument for poll() is 0, or for ppoll() is not a null pointer and > points to a zero-valued timespec structure. > Poll means head you know. As in poll tax, Red poll cattle I am very uncertain in this contex that it means what you think it means -- If you tell a lie big enough and keep repeating it, people will eventually come to believe it. The lie can be maintained only for such time as the State can shield the people from the political, economic and/or military consequences of the lie. It thus becomes vitally important for the State to use all of its powers to repress dissent, for the truth is the mortal enemy of the lie, and thus by extension, the truth is the greatest enemy of the State. Joseph Goebbels
[toc] | [prev] | [next] | [standalone]
| From | Geoff Clare <geoff@clare.See-My-Signature.invalid> |
|---|---|
| Date | 2026-08-18 13:23 +0100 |
| Message-ID | <sevdlm-3o.ln1@ID-313840.user.individual.net> |
| In reply to | #89968 |
The Natural Philosopher wrote: > On 17/08/2026 13:44, Geoff Clare wrote: >> >> Quoting from the SUS at the previously-given URL: >> >> To effect a poll, the application shall ensure that the timeout >> argument for poll() is 0, or for ppoll() is not a null pointer and >> points to a zero-valued timespec structure. >> > Poll means head you know. As in poll tax, Red poll cattle > > I am very uncertain in this contex that it means what you think it means Well, the context is computing and https://foldoc.org/poll says: poll To check the status of an input line, sensor, or memory location to see if a particular external event has been registered. -- Geoff Clare <netnews@gclare.org.uk>
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2026-08-18 17:16 +0100 |
| Message-ID | <11620h1$1v4qd$2@dont-email.me> |
| In reply to | #90059 |
On 18/08/2026 13:23, Geoff Clare wrote: > The Natural Philosopher wrote: > >> On 17/08/2026 13:44, Geoff Clare wrote: >>> >>> Quoting from the SUS at the previously-given URL: >>> >>> To effect a poll, the application shall ensure that the timeout >>> argument for poll() is 0, or for ppoll() is not a null pointer and >>> points to a zero-valued timespec structure. >>> >> Poll means head you know. As in poll tax, Red poll cattle >> >> I am very uncertain in this contex that it means what you think it means > > Well, the context is computing and https://foldoc.org/poll says: > > poll > To check the status of an input line, sensor, or memory location to > see if a particular external event has been registered. > Indeed. but mostly what you do is have an interrupt service routine do that whilst the computer gets on with 'other stuff', The ISR may be a timer like in a multitasking scheduler or it may be triggered by the hardware. What no computer more advanced than a single thread microcontroller ever does is 'poll' the hardware with ISRs disabled -- New Socialism consists essentially in being seen to have your heart in the right place whilst your head is in the clouds and your hand is in someone else's pocket.
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2026-08-17 20:27 +0100 |
| Message-ID | <wwv4igstumh.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #89966 |
Geoff Clare <geoff@clare.See-My-Signature.invalid> writes: > Richard Kettlewell wrote: >> poll() doesn’t poll, despite the name. > > Yes it does, if you tell it to. > > Quoting from the SUS at the previously-given URL: > > To effect a poll, the application shall ensure that the timeout > argument for poll() is 0, or for ppoll() is not a null pointer and > points to a zero-valued timespec structure. Fair point! I’ll amend to “doesn’t _only_ poll”. -- https://www.greenend.org.uk/rjk/
[toc] | [prev] | [standalone]
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
Back to top | Article view | comp.os.linux.misc
csiph-web