Flutterby™! : thing I like about C Code written back

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

thing I like about C Code written back

2024-02-01 01:10:03.193914+01 by Dan Lyke 3 comments

The thing I like about C? Code written back in the '80s compiles just fine. Perl? Same damned thing.

Python? Yeah, they've got tools to manage all of the issues.

C++? Sorry, namespace semantics changed subtly, and will subtly change back, because fuck you, that's why. And deities forbid you should try to find cross-platform ways to use Boost. Just code to POSIX and do your own smart pointer types from the ground up.

[ related topics: Perl Open Source Monty Python Python hubris ]

comments in ascending chronological order (reverse):

#Comment Re: thing I like about C Code written back made: 2024-02-01 04:07:31.392235+01 by: spc476

Unfortunately, there are people who have drunk the C++ Flavor Aid. Sigh.

#Comment Re: thing I like about C Code written back made: 2024-02-01 19:59:59.599149+01 by: Dan Lyke

I think that poster has got a point; at this point having C diverge from a C++ subset feels super weird.

On the other hand, I think I'd be happier with C++ if it had stopped at v1. I kinda like templates, sometimes, though most of that can be done with the preprocessor, but namespacing is a fucking nightmare.

#Comment Re: thing I like about C Code written back made: 2024-02-01 22:39:50.846754+01 by: spc476

As someone who doesn't care to use C++ at all, I don't mind that C has diverged from C++. Heck, spoken language does that—French and Spanish both diverged from Latin after all.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.