Saturday, January 11, 2020

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

"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Jan 11 03:08PM -0800

On 12/18/2019 1:34 PM, Mr Flibble wrote:
> vec2 v2 = v1.xy;
> double z = v1.z;
> vec4 v3 = v1.xyzz;
[...]
 
Almost getting enough time to try it out. Its an interesting go at the
problem. Fwiw, here is a new animation that can benefit from this in C++:
 
https://youtu.be/Q6lJqIl-Nvs
David Brown <david.brown@hesbynett.no>: Jan 11 11:59PM +0100

On 11/01/2020 19:50, Ian Collins wrote:
 
>> (Of course there will often be stages in development where it is fine to
>> check in untested code.)
 
> Are there?
 
Of course. Even if you are doing test-driven development, when you are
very rigid (some might say "obsessed" or "fanatic") on everything being
tested at the earliest possible moment, it is surely possible that you
want to store things away in your version control system despite being
only half-done.
 
But if you are using other development methodologies, it is entirely
reasonable to untested code checked in. You'd likely put it in a
development or private branch rather than a master branch, but you'd
still want it checked in if it represents significant effort or if it
should be shared with others.
David Brown <david.brown@hesbynett.no>: Jan 11 11:53PM +0100

On 11/01/2020 16:05, Daniel wrote:
>> line-delimited or newline-delimited JSON.
 
> But what would you have been referring to? This one?
 
> https://github.com/ndjson/ndjson-spec
 
That one would be fine. But it is such a simple extension or addition
to JSON that it can be described in a paragraph.
 
 
> For interoperability it's preferred to refer to an Internet Standards
> Document, but it doesn't seem an RFC exists yet for this one.
 
Yes, it would be nice to see it incorporated as part of the JSON
standard. (It is far too simple for the bureaucracy of its own
standard, IMHO.)
 
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: