Thursday, August 27, 2020

Digest for comp.lang.c++@googlegroups.com - 8 updates in 4 topics

Vir Campestris <vir.campestris@invalid.invalid>: Aug 27 10:09PM +0100

On 26/08/2020 23:09, James Kuyper wrote:
> Well, he's asking a question about cmake in a forum devoted to C++
> rather than, for instance,<https://discourse.cmake.org/> - what can you
> expect.
 
Sympathy.
 
I've used cmake in the past. My experience is that when it works, it's
great. But when it goes wrong it's impossible to debug.
 
I think he'd agree!
 
Andy
legalize+jeeves@mail.xmission.com (Richard): Aug 27 09:18PM

[Please do not mail me a copy of your followup]
 
Vir Campestris <vir.campestris@invalid.invalid> spake the secret code
 
>I've used cmake in the past. My experience is that when it works, it's
>great. But when it goes wrong it's impossible to debug.
 
This is pretty much true for all build systems.
 
However, CMake is widely used and lots of people have enough expertise
in it to help you solve almost any build problem with CMake.
 
The same can't be said for other build systems that solve the same
problems as CMake. I don't include make in this category because to
get to the same level of support as CMake, make alone doesn't cut it.
You need a portability layer of your own functions on top of make in
order to achieve the same level of functionality. ...and when I type
"make" I'm talking specifically about GNU make.
--
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
The Terminals Wiki <http://terminals-wiki.org>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
Vir Campestris <vir.campestris@invalid.invalid>: Aug 27 10:14PM +0100

On 24/08/2020 22:56, James Kuyper wrote:
> No padding is allowed between consecutive elements in an array.
 
OK, thanks. And those old mainframes with funny word sizes (I've used 24
and 36 bits) are dead and not mourned :)
 
Andy
--
FWIW ICL 1900 and DECSystem10. And neither of them with C or C++!
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Aug 27 11:07AM -0700


>> Fwiw, check this out, a little experiment:
 
>> https://youtu.be/P_lAP4IiYyE
 
> Not really in the same league tbh :)
 
Yeah. I can do better! :^)
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Aug 27 11:38AM -0700


>> Fwiw, check this out, a little experiment:
 
>> https://youtu.be/P_lAP4IiYyE
 
> Not really in the same league tbh :)
 
Here is another one of my favorites:
 
https://youtu.be/hIItHzm9hzc
Vir Campestris <vir.campestris@invalid.invalid>: Aug 27 10:05PM +0100

On 25/08/2020 06:21, Bonita Montero wrote:
>> Well the guys at Microsoft told me that they compile with optimisation
>> for size. Because "A page fault can ruin your day".
 
> We're talking about I-cache hit-rates and not about page-faults.
 
Doesn't matter. Make the code smaller and it will fit in RAM and not be
paged to disk. Or fit in the L2 cache, and not in main store. Or the L1
cache.
 
Andy
Juha Nieminen <nospam@thanks.invalid>: Aug 27 06:16PM

> backwards?
 
> It seems to me that people must have reacted to the 24 Hz Hobbit and
> found the 48 Hz Hobbit more acceptable, yes?
 
No, people complained about the 48 Hz version.
 
When you are not used to it, it looks too smooth, too "clean", too much
like TV rather than a movie. If you have watched 24 Hz movies your entire
life, it looks really unnatural, a bit uncanney.
 
You get used to it very fast, though. By the end of the movie it stops
being distracting and bothering.
"daniel...@gmail.com" <danielaparker@gmail.com>: Aug 27 11:57AM -0700

On Thursday, August 27, 2020 at 2:00:49 PM UTC-4, David Brown wrote:
 
> effect in many areas - the most obvious case being in audio hifi. When
> CD's came out, people complained they sounded "artificial" compared to
> records, when they were actually more accurate.
 
Not so. Vinyl allows for the playback of frequencies over 20 kHz,
16/44.1 CD does not.
 
Daniel
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com.

No comments: