Re: Naming convention for structs and types

From	David Brown <david.brown@hesbynett.no>
Newsgroups	comp.lang.c
Subject	Re: Naming convention for structs and types
Date	2017-01-18 11:03 +0100
Organization	A noiseless patient Spider
Message-ID	<o5nedq$ce4$1@dont-email.me> (permalink)
References	(18 earlier) <o5m05b$gpe$1@dont-email.me> <87fukh2ynd.fsf@gmail.com> <o5m2qk$r0n$1@dont-email.me> <874m0xgslm.fsf@bsb.me.uk> <o5md1m$q0$1@dont-email.me>

Show all headers | View raw

On 18/01/17 01:33, BartC wrote:
> On 17/01/2017 23:43, Ben Bacarisse wrote:
>> BartC <bc@freeuk.com> writes:
> 
> [Unix vs. Windows - sort of]
>>
>> It's not that that chaos does not cause problems -- it does, lots of
>> then -- it's that there is nothing you can do about other than sit back
>> or step up -- you can't petition the bishop to issue an edict.  You will
>> find endless things to moan about in the chaos, but the only answers
>> that make any philosophical sense are "don't use it", "configure it" or
>> "write a better version".
> 
> It's a refreshing change for someone to acknowledge that Unix might not
> be perfect after all!

Given what I and others have posted here, that statement is borderline
insulting.

Certainly I have taken pains to describe differences between "the
Windows Way" and "the Unix Way" as just that - /differences/.  I have
made it clear that I often /prefer/ the *nix way, but that sometimes or
for some purposes I think the Windows way is better.  I have often given
reasons for why a particular facet of *nix (or gcc, since you like to
view them as intertwined) is big, complex or slow - that is far from
saying that it is "perfect" that it is big, slow or complex.  It is
merely saying that it is understandable, and not a problem.

> 
>> Given all you've posted on these things, I can't help wondering why on
>> earth you are using a Linux flavour at all.

Actually, it is more of a wonder that you are using C, which you are
determined to misunderstand and hate.

> 
> People seem to want to defend these things to the death (eg. case
> sensitivity of the OS,

That is a good thing, IMHO.  Your preferences may vary - that's what
preferences do.

 the chaos that typing 'man *' may cause, the

I can think of plenty of ways to cause chaos on a computer, Linux or
Windows.  Asking the machine to display all the documentation it has for
all the software installed is going to be a demanding task.
Fortunately, it's not a problem because it is a pointless thing to do.

> disseminated file system,

The filessytem organisation in Linux is not perfect, but it's not bad.
Clearly it can be confusing when you are not familiar with it, and are
unable to google for "overview of the Linux filesystem organisation".

The Windows organisation is much, much worse.  It is full of hidden
directories, fake directories that look different depending on which
user is accessing them or which program, huge directories within the
c:\windows hierarchy whose very size slows down the system, "temp"
directories that swell up with tens of thousands of files that are not
cleared up automatically and are very hard to clear manually, directory
names of ridiculous lengths full of "unfriendly" characters like spaces
and brackets, on an OS that has a 260 character limit on the total path
length.

> lack of standards for character

For most low-level aspects, *nix does not care about what character set
you use.  For user interaction, you usually have good UTF-8 support,
character entry, fonts, etc., right out of the box.

> /non-blocking
> keyboard i/o and basic console i/o, the fantastically elaborate gcc
> suite of compilers, 

Yes, gcc is fantastic!

In comparison, the standard Windows programming tools are ... nothing.
There is nothing installed by default, nothing that exists as a
standard, either for C or any other programming language.

The closest contender is MSVC - and it's size and complexity makes gcc
look like tcc in comparison.  Yes, MSVC includes much more than just the
compiler (and if you like its IDE and debugger, great).

> complete dependence on 'make' 

"make" is an extraordinarily useful tool, and has shown its use over
decades.  I couldn't do my job on Windows without it.  There is no doubt
that some aspects of make's syntax are really tangled and complex, and
some are just downright /wrong/ (such as needing tab characters for some
indents, rather than allowing spaces).  You can see this in the number
of "make alternatives" that have appeared over the years.  You can also
note that despite all these alternatives, "make" is still very popular.

> and the non-portable
> 'configure').

"configure" exists precisely to make software portability simpler.  But
it is mainly portability between *nix systems.  And yes, it is outdated,
overly complex, and far, far slower than it need be.

> Almost as though they take pride in knowing all this
> arcane stuff.
> 

I think most people rather take pride in knowing what they find useful,
being willing to try something new, and being able to find the missing
details when they need it.

> I prefer Windows but if it merits it I will criticise that too.

I fully understand preferences - I just wish you would understand that
it /is/ a preference, not some sort of absolute fact.  I use both Linux
and Windows daily, and /prefer/ Linux for most of what I do (both at
work and for leisure).  But some things are easier, more efficient, or
more convenient in Windows - both are useful.

Sometimes I ride my bike, sometimes I take my car.  Both will transport
me around locally.  But I don't moan that the bike is badly designed or
chaotic because it uses a bar for steering rather than a wheel.

> 
>> Nothing about it seems to
>> suit your preferences or coincide with your intuition, and I don't get
>> the feeling that you are forced to use it for work.

A key problem Bart has is that he thinks his preferences and familiarity
/are/ his "intuition", and that /his/ intuition is /everyone's/
intuition.  He believes case-insensitive filing systems are "intuitive"
and case-sensitive systems are "non-intuitive", when it is nothing more
or less than his own familiarity.

For people with a wide experience in computing, moving between Windows
and Linux (or vice versa) is not a problem.  There are always some
things that take a little longer to find or learn, and some things that
cause irritation, but you quickly find practical solutions or workarounds.

For people with little computer experience, moving between systems is
not a problem either.  Once someone has told you how to start your
browser or email program, you're good to go.

The trouble is for power-users with great familiarity with one system,
and who are determined to "prove" that the other system is worse in all
possible ways.  That is your category, Bart.  You intentionally and
knowingly pick the smallest and cheapest Linux system you can find,
intentionally and knowingly using an unfamiliar processor.  You
repeatedly pick on differences (usually totally negligible things) that
you label as "problems" and complain about loudly rather than spending
30 seconds reading about it.  You are much like a long-term Linux user
buying a "MS Surface" and complaining about poor support for a second
monitor, no built-in development tools, and how counter-intuitive it is
to type "ipconfig" when everyone would naturally type "ifconfig".

> 
> There were also scare stories a few years ago that it would be
> impossible to develop programs for new Windows OSes using your own tools
> (making it as hard as doing stuff for iPad/iPhone or Android). I didn't
> want to quit coding just yet, and Linux seemed to be the only option (as
> I can't and don't want to do hardware any more).
> 
>> The simplest
>> solution would be just to leave it alone.  The objective of the bazaar
>> is not to dominate the skyline and win converts, but simply to provide a
>> home for diverse solutions where you might find something of value.  I
>> don't think you have found anything of value there.
> 
> I don't agree. I think the OS is usable once a set of problems have been
> solved. But I haven't been impressed with what I'm discovering on the
> way. In the meantime, the need for portability, to need to work on
> either OS, means the quality of my coding has improved.
> 

Once you open your mind to "differences" rather than "problems", you
will get on far better.

Thread

Naming convention for structs and types "Fernando D. Bozzo" <fdbozzo@gmail.com> - 2017-01-12 11:48 -0800
  Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-12 11:58 -0800
    Re: Naming convention for structs and types Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-13 01:35 +0000
      Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-12 17:43 -0800
      Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-13 02:19 +0000
      Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-12 19:26 -0800
        Re: Naming convention for structs and types "Fernando D. Bozzo" <fdbozzo@gmail.com> - 2017-01-13 00:28 -0800
        Re: Naming convention for structs and types Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-13 10:56 +0000
          Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-16 12:23 -0800
        Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 12:49 +0100
          Re: Naming convention for structs and types Thiago Adams <thiago.adams@gmail.com> - 2017-01-13 05:03 -0800
            Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 16:00 +0100
              Re: Naming convention for structs and types Thiago Adams <thiago.adams@gmail.com> - 2017-01-13 18:28 -0800
                Re: Naming convention for structs and types supercat@casperkitty.com - 2017-01-13 18:58 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-14 14:07 +0100
                Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-14 14:31 -0800
          Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-13 09:20 -0800
            Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 18:47 +0100
              Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-13 10:02 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 21:42 +0100
                Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-13 12:55 -0800
                Re: Naming convention for structs and types supercat@casperkitty.com - 2017-01-13 13:09 -0800
                Re: Naming convention for structs and types Tim Rentsch <txr@alumni.caltech.edu> - 2017-01-15 21:01 -0800
    Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-12 17:48 -0800
      Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-12 19:35 -0800
        Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-12 19:45 -0800
          Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-12 19:51 -0800
            Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-12 21:12 -0800
            Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 12:53 +0100
              Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-13 08:59 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 18:48 +0100
                Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-13 18:03 -0800
                Re: Naming convention for structs and types raltbos@xs4all.nl (Richard Bos) - 2017-01-18 12:05 +0000
    Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-13 19:30 +1300
      Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-13 13:00 +0000
        Re: Naming convention for structs and types Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-13 10:43 -0800
          Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-13 18:52 +0000
            Re: Naming convention for structs and types Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-13 12:56 -0800
              Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-14 10:54 +1300
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-13 22:00 +0000
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-14 11:18 +1300
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-14 00:59 +0000
                Re: Naming convention for structs and types Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-13 17:12 -0800
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-14 14:47 +1300
                Re: Naming convention for structs and types Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-14 01:36 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-14 11:26 +0000
                Re: Naming convention for structs and types Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-14 14:11 +0000
                Re: Naming convention for structs and types Parity Error <kgf@quiscurat.net> - 2017-01-15 08:33 +0000
                Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-15 02:52 -0800
                Re: Naming convention for structs and types Jean-Marc Bourguet <jm@bourguet.org> - 2017-01-15 14:48 +0100
                Re: Naming convention for structs and types raltbos@xs4all.nl (Richard Bos) - 2017-01-18 12:07 +0000
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-14 14:40 +1300
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-14 11:28 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-14 11:48 +0000
                Re: Naming convention for structs and types Jean-Marc Bourguet <jm@bourguet.org> - 2017-01-14 13:17 +0100
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-14 14:21 +0100
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-14 13:27 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-14 14:00 +0000
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-14 14:11 +0000
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-14 14:12 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-14 16:18 +0100
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-14 16:31 +0000
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-14 18:50 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-14 19:48 +0000
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-15 10:15 +1300
                Re: Naming convention for structs and types Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-14 20:12 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-14 23:31 +0100
                Re: Naming convention for structs and types Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-14 10:28 -0800
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-14 18:52 +0000
                Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-14 14:49 -0800
                Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-14 14:41 -0800
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-14 23:03 +0000
                Re: Naming convention for structs and types Parity Error <kgf@quiscurat.net> - 2017-01-15 08:41 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-16 20:01 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-17 00:19 +0100
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-17 00:29 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-17 09:12 +0100
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-17 11:59 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-17 13:16 +0000
                OT: Bash tab completion (was: Naming convention for structs and types) Andreas Perstinger <andipersti@gmail.com> - 2017-01-17 13:27 +0000
                Re: OT: Bash tab completion BartC <bc@freeuk.com> - 2017-01-17 13:59 +0000
                Re: OT: Bash tab completion David Brown <david.brown@hesbynett.no> - 2017-01-17 15:49 +0100
                Re: OT: Bash tab completion fir <profesor.fir@gmail.com> - 2017-01-17 07:06 -0800
                Re: OT: Bash tab completion fir <profesor.fir@gmail.com> - 2017-01-17 07:43 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-17 15:18 +0100
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-17 19:26 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-17 21:53 +0100
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-17 20:56 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-17 21:38 +0000
                Re: Naming convention for structs and types fir <profesor.fir@gmail.com> - 2017-01-17 14:22 -0800
                Re: Naming convention for structs and types Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-17 23:43 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-18 00:33 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 11:03 +0100
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-18 12:15 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 13:59 +0100
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-18 15:45 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 17:28 +0100
                Re: Naming convention for structs and types supercat@casperkitty.com - 2017-01-18 09:30 -0800
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-18 23:18 +1300
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-17 21:22 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 12:47 +0100
                Re: Naming convention for structs and types fir <profesor.fir@gmail.com> - 2017-01-18 08:11 -0800
                Re: Naming convention for structs and types raltbos@xs4all.nl (Richard Bos) - 2017-01-18 17:17 +0000
                Re: Naming convention for structs and types fir <profesor.fir@gmail.com> - 2017-01-18 09:47 -0800
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-18 21:20 +0000
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-18 22:26 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-19 00:31 +0100
                Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-18 15:41 -0800
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-18 23:58 +0000
                Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-17 11:49 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-17 21:56 +0100
                Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-17 13:18 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 12:50 +0100
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-18 07:51 +1300
                Re: Naming convention for structs and types BartC <bc@freeuk.com> - 2017-01-17 19:50 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-17 21:59 +0100
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-18 17:51 +1300
                Re: Naming convention for structs and types raltbos@xs4all.nl (Richard Bos) - 2017-01-18 12:15 +0000
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-19 07:52 +1300
                Re: Naming convention for structs and types raltbos@xs4all.nl (Richard Bos) - 2017-01-18 12:09 +0000
                Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-14 13:26 +0000
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-15 08:10 +1300
                Re: Naming convention for structs and types Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-14 12:28 -0800
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-15 10:17 +1300
                Re: Naming convention for structs and types Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-13 15:12 -0800
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-14 12:31 +1300
                Re: Naming convention for structs and types Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-01-13 16:03 -0800
          Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-13 15:57 -0800
            Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-14 13:29 -0800
        Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-14 10:45 +1300
      Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-16 12:19 -0800
        Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-16 15:22 -0800
          Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-16 16:35 -0800
            Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-17 17:02 -0800
        Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-17 20:57 +1300
          Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-17 08:47 +0000
            Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-18 08:03 +1300
          Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-17 07:04 -0800
            Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-18 08:01 +1300
              Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-17 11:47 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-17 22:16 +0100
                Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-17 15:44 -0800
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-18 17:59 +1300
                Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-18 04:42 -0800
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-19 07:57 +1300
                Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-18 11:22 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 13:36 +0100
                Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-18 05:07 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 16:09 +0100
                Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-18 07:36 -0800
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-18 17:32 +0100
                Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-18 17:55 +1300
            Re: Naming convention for structs and types "Chris M. Thomasson" <invalid@invalid.invalid> - 2017-01-19 22:28 -0800
              Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-20 08:36 +0000
              Re: Naming convention for structs and types "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-20 04:27 -0800
  Re: Naming convention for structs and types luser droog <luser.droog@gmail.com> - 2017-01-12 12:01 -0800
    Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-12 20:11 +0000
      Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-12 12:50 -0800
        Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-12 21:02 +0000
          Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-12 13:26 -0800
            Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-12 21:35 +0000
      Re: Naming convention for structs and types luser droog <luser.droog@gmail.com> - 2017-01-12 16:37 -0800
      Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 12:57 +0100
        Re: Naming convention for structs and types Gareth Owen <gwowen@gmail.com> - 2017-01-13 16:38 +0000
          Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-13 17:52 +0100
  Re: Naming convention for structs and types Richard Heathfield <rjh@cpax.org.uk> - 2017-01-12 20:07 +0000
  Re: Naming convention for structs and types Thiago Adams <thiago.adams@gmail.com> - 2017-01-12 12:45 -0800
  Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-12 13:01 -0800
  Re: Naming convention for structs and types jadill33@gmail.com - 2017-01-12 13:57 -0800
  Re: Naming convention for structs and types John Bode <jfbode1029@gmail.com> - 2017-01-12 13:59 -0800
    Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-12 15:08 -0800
    Re: Naming convention for structs and types Tim Rentsch <txr@alumni.caltech.edu> - 2017-01-14 10:33 -0800
      Re: Naming convention for structs and types Keith Thompson <kst-u@mib.org> - 2017-01-14 15:20 -0800
        Re: Naming convention for structs and types Tim Rentsch <txr@alumni.caltech.edu> - 2017-01-15 21:31 -0800
  Re: Naming convention for structs and types Ian Collins <ian-news@hotmail.com> - 2017-01-13 19:43 +1300
    Re: Naming convention for structs and types "Fernando D. Bozzo" <fdbozzo@gmail.com> - 2017-01-13 01:00 -0800
      Re: Naming convention for structs and types James Kuyper <jameskuyper@verizon.net> - 2017-01-13 13:03 -0500
        Re: Naming convention for structs and types "Fernando D. Bozzo" <fdbozzo@gmail.com> - 2017-01-13 16:02 -0800
        Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-14 13:36 +0100
          Re: Naming convention for structs and types "Fernando D. Bozzo" <fdbozzo@gmail.com> - 2017-01-14 05:22 -0800
            Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-14 17:27 +0100
          Re: Naming convention for structs and types raltbos@xs4all.nl (Richard Bos) - 2017-01-18 21:05 +0000
            Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-19 09:48 +0100
              Re: Naming convention for structs and types James Kuyper <jameskuyper@verizon.net> - 2017-01-19 13:31 -0500
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-19 21:18 +0100
              Re: Naming convention for structs and types raltbos@xs4all.nl (Richard Bos) - 2017-01-22 17:10 +0000
                Re: Naming convention for structs and types David Brown <david.brown@hesbynett.no> - 2017-01-22 18:27 +0100
    Re: Naming convention for structs and types James Kuyper <jameskuyper@verizon.net> - 2017-01-13 12:49 -0500
      Re: Naming convention for structs and types supercat@casperkitty.com - 2017-01-13 09:55 -0800
  Re: Naming convention for structs and types "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2017-01-13 23:46 +0800

csiph-web