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


Groups > comp.lang.c > #381780 > unrolled thread

What I've learned in comp.lang.c

Started bybart <bc@freeuk.com>
First post2024-02-05 01:09 +0000
Last post2024-02-05 23:29 +0000
Articles 13 on this page of 133 — 16 participants

Back to article view | Back to comp.lang.c


Contents

  What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-05 01:09 +0000
    Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-05 05:58 +0000
      Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-04 22:49 -0800
        Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-05 07:03 +0000
          Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-04 23:51 -0800
            Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-04 23:52 -0800
              Re: What I've learned in comp.lang.c Jan van den Broek <balglaas@dds.nl> - 2024-02-05 08:36 +0000
      Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-05 18:23 +0200
      Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-05 18:32 +0200
        Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-05 20:53 +0100
          Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-05 20:53 +0000
            Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-06 09:44 +0100
              Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-06 01:03 -0800
              Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-06 13:41 +0200
                Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-06 13:08 +0100
              Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-06 23:23 +0000
                Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 08:54 +0100
                  Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-07 08:59 +0000
                    Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-07 10:47 +0000
                      Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 11:04 +0000
                        Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 14:21 +0100
                          Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 14:24 +0000
                            Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 21:30 +0100
                        Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-07 15:36 +0000
                          Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 18:05 +0000
                            Re: What I've learned in comp.lang.c scott@slp53.sl.home (Scott Lurndal) - 2024-02-07 18:26 +0000
                              Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 19:53 +0000
                                Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-07 21:38 +0000
                                  Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-08 00:29 +0000
                            Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 21:37 +0100
                              Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 22:52 +0000
                                Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-08 01:13 +0000
                                  Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-08 02:09 +0000
                                    Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-08 03:07 +0000
                                      Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-08 14:17 +0000
                                    Re: What I've learned in comp.lang.c Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-08 16:02 -0800
                                      Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-09 00:48 +0000
                                        Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-09 08:53 +0100
                                        Re: What I've learned in comp.lang.c Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-10 21:55 -0800
                                Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-08 13:01 +0100
                            Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-08 11:37 +0000
                              Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-08 12:10 +0000
                                Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-08 13:24 +0100
                                  Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-08 13:03 +0000
                                  Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-08 13:17 +0000
                                    Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-08 16:52 +0100
                                Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-08 17:17 +0000
                              Re: What I've learned in comp.lang.c Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-09 14:50 -0800
                      Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-07 12:44 +0000
                        Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 14:49 +0100
                        Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-07 16:13 +0000
                        Re: What I've learned in comp.lang.c Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-02-07 08:21 -0800
                    Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 14:01 +0100
                      Re: What I've learned in comp.lang.c Richard Harnden <richard.nospam@gmail.invalid> - 2024-02-07 13:21 +0000
                      Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-07 13:42 +0000
                        Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 16:17 +0100
                      Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-07 21:34 +0000
                    Re: What I've learned in comp.lang.c scott@slp53.sl.home (Scott Lurndal) - 2024-02-07 16:21 +0000
                      Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-08 13:26 +0200
                  Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-07 10:04 +0000
                    Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 14:51 +0100
                      Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-07 15:30 +0000
                        Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-07 15:45 +0000
                          Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 21:44 +0100
                            Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-08 00:33 +0000
                              Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-08 01:30 +0000
                              Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-08 01:38 +0000
                                Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-08 02:21 +0000
                                  Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-08 03:07 +0000
                          Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-08 11:45 +0000
                            Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-08 12:15 +0000
                              Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-08 13:29 +0100
                                Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-08 12:55 +0000
                                  Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-09 09:02 +0100
                                Re: What I've learned in comp.lang.c scott@slp53.sl.home (Scott Lurndal) - 2024-02-08 16:09 +0000
                                  Re: What I've learned in comp.lang.c Richard Harnden <richard.nospam@gmail.invalid> - 2024-02-08 16:28 +0000
                                  Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-08 17:13 +0000
                        Re: What I've learned in comp.lang.c Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-08 17:53 -0800
      Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-05 19:02 +0200
        Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-05 23:28 +0000
          Re: What I've learned in comp.lang.c Richard Harnden <richard.nospam@gmail.invalid> - 2024-02-05 23:40 +0000
          Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-06 01:46 +0200
            Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-06 09:54 +0100
          Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-05 16:03 -0800
            Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-05 16:06 -0800
          Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-06 09:50 +0100
            Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-06 01:01 -0800
            Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-06 23:24 +0000
              Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 08:56 +0100
                Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-07 12:09 +0200
                  Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 15:03 +0100
                Re: What I've learned in comp.lang.c scott@slp53.sl.home (Scott Lurndal) - 2024-02-07 16:25 +0000
                  Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 21:49 +0100
                    Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-07 13:04 -0800
                    Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-07 23:37 +0200
                      Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-08 08:52 +0100
                        Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-09 15:55 +0200
                          Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-09 15:29 +0100
                            Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-09 16:52 +0200
                              Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-09 17:22 +0100
                                Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-10 07:18 +0000
                                  Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-10 17:11 +0100
                                    Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-10 21:23 +0000
                                      Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-11 14:01 +0100
                  Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-07 21:41 +0000
      Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 02:18 +0000
        Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-07 09:30 +0100
        Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-07 09:04 +0000
        Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-07 23:24 +0000
          Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-08 01:46 +0000
            Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-08 02:50 +0000
              Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-08 11:08 +0000
              Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-08 13:10 +0200
                Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-08 17:48 +0000
                  Re: What I've learned in comp.lang.c Michael S <already5chosen@yahoo.com> - 2024-02-08 21:30 +0200
                  Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-08 20:39 +0000
                  Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-08 13:39 -0800
                    Re: What I've learned in comp.lang.c Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-02-08 14:18 -0800
                      Re: What I've learned in comp.lang.c gazelle@shell.xmission.com (Kenny McCormack) - 2024-02-08 22:29 +0000
                        Re: What I've learned in comp.lang.c "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-08 14:43 -0800
                          Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-09 09:12 +0100
    Re: What I've learned in comp.lang.c Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-04 23:36 -0800
      Re: What I've learned in comp.lang.c scott@slp53.sl.home (Scott Lurndal) - 2024-02-05 14:52 +0000
        Re: What I've learned in comp.lang.c gazelle@shell.xmission.com (Kenny McCormack) - 2024-02-05 22:58 +0000
      Re: What I've learned in comp.lang.c Jim Jackson <jj@franjam.org.uk> - 2024-02-05 18:01 +0000
    Re: What I've learned in comp.lang.c Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-02-05 08:29 +0000
      Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 01:35 +0000
        Re: What I've learned in comp.lang.c Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-07 02:26 +0000
          Re: What I've learned in comp.lang.c bart <bc@freeuk.com> - 2024-02-07 10:47 +0000
    Re: What I've learned in comp.lang.c Dan Purgert <dan@djph.net> - 2024-02-05 11:03 +0000
    Re: What I've learned in comp.lang.c David Brown <david.brown@hesbynett.no> - 2024-02-05 13:15 +0100
      Re: What I've learned in comp.lang.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-02-05 14:09 +0000
    Re: What I've learned in comp.lang.c Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-02-05 23:29 +0000

Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]


#382167

FromDavid Brown <david.brown@hesbynett.no>
Date2024-02-09 09:12 +0100
Message-ID<uq4moj$2hive$3@dont-email.me>
In reply to#382142
On 08/02/2024 23:43, Chris M. Thomasson wrote:
> On 2/8/2024 2:29 PM, Kenny McCormack wrote:
>> In article <87il2yfvmp.fsf@nosuchdomain.example.com>,
>> Keith Thompson  <Keith.S.Thompson+u@gmail.com> wrote:
>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:
>>>> On 2/8/2024 9:48 AM, Kaz Kylheku wrote:
>>>>> On 2024-02-08, Michael S <already5chosen@yahoo.com> wrote:
>>>> [...]
>>>>> LOL, even a 400 kilobyte assembler is bat shit crazy.
>>>>> Can you imagine working with that on a 512 Kb IBM PC?
>>>>
>>>> This assembler was pretty small... ;^D
>>>>
>>>> https://youtu.be/bCSDkjhVM2A
>>>
>>> Please keep doing this.
>>
>> "Introduction to Assembly Language Programming on the Apple IIgs - 
>> Lesson 1"
>>
> 
> Yup. I forgot to put in the title. Sorry everybody. ;^o

Be assured that almost no one will want to follow these links, even if 
they know the title.  And I think everyone here is capable of using 
google, and of using Youtube's search.  If someone reads a post here 
mentioning assembly and thinks they'd like to spend a half hour watching 
a history video on assembly programming on old computers, then they will 
manage that fine.

Please do not post these links - with or without titles - unless they 
are extremely relevant and somehow outstanding videos that add so much 
to the thread that they are worth watching.  And even then, accompany 
the link with information, a summary and justification for the link.

I appreciate your many positive contributions to discussions in c.l.c. 
and c.l.c++, and your knowledge and opinions on threading and 
synchronisation.  But I doubt if anyone is interested in yet another 
"This made me think of <https://youtu.be..." post.  (And while we are at 
it, please stop the pissing contests with Bonita on c.l.c++.  Take your 
pantomime fights to email, or drop them altogether.)

Thanks.

(Cue stupid comment from Kenny as a follow-up.)

[toc] | [prev] | [next] | [standalone]


#381800

FromTim Rentsch <tr.17687@z991.linuxsc.com>
Date2024-02-04 23:36 -0800
Message-ID<86jznj746w.fsf@linuxsc.com>
In reply to#381780
bart <bc@freeuk.com> writes:

> [...]
>
> * Hardly anybody here has a project which can be built simply by
> compiling and linking all the modules.

Not everyone is working on a project where the deliverable is a
single executable.  It's much more difficult to work on a project
where the deliverables form a set of related files that make up a
third-party library, and target multiple platforms.

> Even Tim Rentsch's simplest project has a dizzying set of special
> requirements.

This statement is a misrepresentation, and undoubtedly a deliberate
one.  Furthermore how it is expressed is petty and childish.

[toc] | [prev] | [next] | [standalone]


#381818

Fromscott@slp53.sl.home (Scott Lurndal)
Date2024-02-05 14:52 +0000
Message-ID<XC6wN.397626$p%Mb.396054@fx15.iad>
In reply to#381800
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
>bart <bc@freeuk.com> writes:
>
>> [...]
>>
>> * Hardly anybody here has a project which can be built simply by
>> compiling and linking all the modules.
>
>Not everyone is working on a project where the deliverable is a
>single executable.  It's much more difficult to work on a project
>where the deliverables form a set of related files that make up a
>third-party library, and target multiple platforms.
>
>> Even Tim Rentsch's simplest project has a dizzying set of special
>> requirements.
>
>This statement is a misrepresentation, and undoubtedly a deliberate
>one.  Furthermore how it is expressed is petty and childish.

I have reached the point where it's not worth my time to respond
to bart, even to correct his misrepresentations of what I and
other have said.

[toc] | [prev] | [next] | [standalone]


#381864

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2024-02-05 22:58 +0000
Message-ID<uprp6o$utqu$1@news.xmission.com>
In reply to#381818
In article <XC6wN.397626$p%Mb.396054@fx15.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
...
>I have reached the point where it's not worth my time to respond
>to bart, even to correct his misrepresentations of what I and
>other have said.

Being killfiled by Scotty is almost as good a thing as being kf'd by
Keith.  Keep it up!

-- 
Life's big questions are big in the sense that they are momentous. However, contrary to
appearances, they are not big in the sense of being unanswerable. It is only that the answers
are generally unpalatable. There is no great mystery, but there is plenty of horror.
    (https://en.wikiquote.org/wiki/David_Benatar)

[toc] | [prev] | [next] | [standalone]


#381837

FromJim Jackson <jj@franjam.org.uk>
Date2024-02-05 18:01 +0000
Message-ID<slrnus28kb.2s0.jj@iridium.wf32df>
In reply to#381800
On 2024-02-05, Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:
> bart <bc@freeuk.com> writes:
>
>> [...]
>>
>> * Hardly anybody here has a project which can be built simply by
>> compiling and linking all the modules.
>
> Not everyone is working on a project where the deliverable is a
> single executable.  It's much more difficult to work on a project
> where the deliverables form a set of related files that make up a
> third-party library, and target multiple platforms.
>
>> Even Tim Rentsch's simplest project has a dizzying set of special
>> requirements.
>
> This statement is a misrepresentation, and undoubtedly a deliberate
> one.  Furthermore how it is expressed is petty and childish.

Did you expect anything else?

[toc] | [prev] | [next] | [standalone]


#381803

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2024-02-05 08:29 +0000
Message-ID<upq69d$7999$1@dont-email.me>
In reply to#381780
On 05/02/2024 01:09, bart wrote:
> 
> In no particular order.
> 
> * Software development can ONLY be done on a Unix-related OS
> 
> * It is impossible to develop any software, let alone C, on pure Windows
> 
> * You can spend decades developing and implementing systems languages at 
> the level of C, but you still apparently know nothing of the subject
> 

The tone's currently rather bad, and somehow it has developed that you 
and I are on one side and pretty much everyone else on the other. We 
both have open source projects which are or at least attempt to be 
actually useful to other people, whilst I don't think many of the others 
can say that, and maybe that's the underlying reason. But who knows.

I'm trying to improve the tone. It's hard because people have got lots 
of motivations for posting, and some of them aren't very compatible with 
a good humoured, civilised group. And we've got a lot of bad behaviour, 
not all of it directed at us by any means. However whilst you're very 
critical of other people's design decisions, I've rarely if ever heard 
to say that therefore you criticise someone's general character. But 
finally tolerance has snapped.


-- 
Check out Basic Algorithms and my other books:
https://www.lulu.com/spotlight/bgy1mm

[toc] | [prev] | [next] | [standalone]


#381938

Frombart <bc@freeuk.com>
Date2024-02-07 01:35 +0000
Message-ID<upump8$14ktk$1@dont-email.me>
In reply to#381803
On 05/02/2024 08:29, Malcolm McLean wrote:
> On 05/02/2024 01:09, bart wrote:
>>
>> In no particular order.
>>
>> * Software development can ONLY be done on a Unix-related OS
>>
>> * It is impossible to develop any software, let alone C, on pure Windows
>>
>> * You can spend decades developing and implementing systems languages 
>> at the level of C, but you still apparently know nothing of the subject
>>
> 
> The tone's currently rather bad, and somehow it has developed that you 
> and I are on one side and pretty much everyone else on the other. We 
> both have open source projects which are or at least attempt to be 
> actually useful to other people, whilst I don't think many of the others 
> can say that, and maybe that's the underlying reason. But who knows.
> 
> I'm trying to improve the tone. It's hard because people have got lots 
> of motivations for posting, and some of them aren't very compatible with 
> a good humoured, civilised group. And we've got a lot of bad behaviour, 
> not all of it directed at us by any means. However whilst you're very 
> critical of other people's design decisions, I've rarely if ever heard 
> to say that therefore you criticise someone's general character.
> 


Well we've both posted code of sizeable, actual and practical projects. 
Very few on the 'other side' have. Maybe it's proprietory or there are 
other reasons. But it means their own output can't be criticised here.

Myself I've also pretty much given up on discussing new features for C 
or new directions. The thread on build systems lies outside the 
language. But few regulars are that interested in that side of it; only 
in what C does right now.

 From what I can see, the most fascinating topics for them are pedantic 
details of the C standard, and the most low level technical details of 
Unix-like systems.

 > But finally tolerance has snapped.

I usually argue against ideas not people. But there is only so many 
personal insults that you can take.

[toc] | [prev] | [next] | [standalone]


#381941

FromKaz Kylheku <433-929-6894@kylheku.com>
Date2024-02-07 02:26 +0000
Message-ID<20240206181827.698@kylheku.com>
In reply to#381938
On 2024-02-07, bart <bc@freeuk.com> wrote:
> Well we've both posted code of sizeable, actual and practical projects. 
> Very few on the 'other side' have. Maybe it's proprietory or there are 
> other reasons. But it means their own output can't be criticised here.

Posting large amounts of code into discussion groups isn't practical,
and against netiquette.

The right thing is to host your code somewhere (which it behooves you to
do for obvious other reasons) and post a link to it.

People used to share code via comp.sources.*. Some well-known old
projects first made their appearance that way. E.g. Dick Grune posted
the first version of CVS in what was then called mod.sources in 1986.

-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca

[toc] | [prev] | [next] | [standalone]


#381959

Frombart <bc@freeuk.com>
Date2024-02-07 10:47 +0000
Message-ID<upvn4n$1cnmp$2@dont-email.me>
In reply to#381941
On 07/02/2024 02:26, Kaz Kylheku wrote:
> On 2024-02-07, bart <bc@freeuk.com> wrote:
>> Well we've both posted code of sizeable, actual and practical projects.
>> Very few on the 'other side' have. Maybe it's proprietory or there are
>> other reasons. But it means their own output can't be criticised here.
> 
> Posting large amounts of code into discussion groups isn't practical,
> and against netiquette.
> 
> The right thing is to host your code somewhere (which it behooves you to
> do for obvious other reasons) and post a link to it.
> 
> People used to share code via comp.sources.*. Some well-known old
> projects first made their appearance that way. E.g. Dick Grune posted
> the first version of CVS in what was then called mod.sources in 1986.
> 

Directly including source code as part of a post is not that practical 
beyond a few hundred lines of code.

Clearly that wouldn't count as 'sizeable'. That would need to be done 
via a link.

[toc] | [prev] | [next] | [standalone]


#381805

FromDan Purgert <dan@djph.net>
Date2024-02-05 11:03 +0000
Message-ID<slrnus1g3f.2h7.dan@djph.net>
In reply to#381780
On 2024-02-05, bart wrote:
> [...]
> * Nobody here apparently knows how to build a program consisting purely 
> of C source files, using only a C compiler.

What does this one mean, exactly?  I thought the "compiler" and "linker"
were separate tools used under the umbrella term "compiling".

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860

[toc] | [prev] | [next] | [standalone]


#381807

FromDavid Brown <david.brown@hesbynett.no>
Date2024-02-05 13:15 +0100
Message-ID<upqjgk$9c1f$1@dont-email.me>
In reply to#381780
On 05/02/2024 02:09, bart wrote:
> 
> In no particular order.
> 

<snip>

> 
> Shall I post this pile of crap or not?

No.  It is, after all, a pile of crap.

What we have learned about Bart in c.l.c. :

* Bart generally does not read what other people post.

* Bart exaggerates /everything/ - including things no one ever wrote.

* Bart extrapolates /everything/ to get a binary black-or-white 
all-or-nothing straw man that he can complain about.  If one person says 
they do X and not Y, Bart takes that to mean /everyone/ does X and /no 
one/ does Y.

* Bart prefers tilting at windmills to learning about C, or indeed 
anything in the real world.

* Bart has no interest in what anyone else does, wants or needs.

> 
> I really need to get back to some of those pointless, worthless toy 
> projects of mine.
> 

No, you should go back to doing something you actually /like/.  Stop 
fighting imaginary battles about problems that don't exist.  Stop 
winding yourself into a frenzy over nothing.

You don't like C.  Find something else that you /do/ like, and use that 
instead.

I can't speak for anyone else, but I'd rather you were happily doing 
something you are comfortable with, instead of endless gripes and rants 
here.

[toc] | [prev] | [next] | [standalone]


#381812

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2024-02-05 14:09 +0000
Message-ID<87jznjuhnl.fsf@bsb.me.uk>
In reply to#381807
David Brown <david.brown@hesbynett.no> writes:

> On 05/02/2024 02:09, bart wrote:
>> In no particular order.
>> 
>
> <snip>
>
>> Shall I post this pile of crap or not?
>
> No.  It is, after all, a pile of crap.

Why do you reply so much?  I get why Bart posts, but not why you reply
so much?  It's not as if gcc (to take one but one example) needs to be
defended from people saying it does it all wrong!

He sometimes posts things that, in my opinion, benefit from a reply.
His "C is so mysterious, how can any one use it posts", for example,
benefit from a reply or two that explains what C's rules really are so
that people coming along later will know what the facts of the matter
are.  But there have been none of those lately.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]


#381868

FromLawrence D'Oliveiro <ldo@nz.invalid>
Date2024-02-05 23:29 +0000
Message-ID<uprr01$gcqc$5@dont-email.me>
In reply to#381780
On Mon, 5 Feb 2024 01:09:10 +0000, bart wrote:

> * Software development can ONLY be done on a Unix-related OS

Does the term “butthurt” mean anything to you?

[toc] | [prev] | [standalone]


Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]

Back to top | Article view | comp.lang.c


csiph-web