Wednesday, July 12, 2023

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

Frederick Virchanza Gotham <cauldwell.thomas@gmail.com>: Jul 12 02:51PM -0700

Link to GodBolt:
 
https://godbolt.org/z/KjEbGPWMT
 
And here it is copy-pasted:
 
#include <sstream>
#include <iostream>
#include <utility>
 
using std::stringstream, std::cout, std::endl;
 
void Func(std::stringstream &&arg)
{
static std::stringstream obj;
 
obj = std::move(arg);
 
cout << obj.str() << endl;
}
 
int main(void)
{
std::stringstream ss;
 
for ( unsigned i = 0u; i < 8u; ++i )
{
ss << i;
 
Func( std::move(ss) );
}
}
 
 
Should this code work properly on every implementation of the C++23 standard?
"Fred. Zwarts" <F.Zwarts@HetNet.nl>: Jul 12 10:19AM +0200

Op 11.jul..2023 om 19:04 schreef Scott Lurndal:
>> a reasonable choice,
 
> So was unix and later Linux with NFS. A far superior protocol
> compared with SMB.
 
Superior in terms of performance, but in terms of authentication SMB was
far superior. Kerberos authentication was added to NFS much later.
scott@slp53.sl.home (Scott Lurndal): Jul 12 02:27PM

>On 7/11/2023 12:48 PM, David Brown wrote:
>> On 11/07/2023 20:49, Scott Lurndal wrote:
 
<valid points from David, pointing out that my experiences have
generally been more towards the data center than SMB>
 
 
>Fwiw, Ken Williams had to blow some serious coin on some silicon
>graphics workstations to create the game Phantasmagoria. Iirc, it was
>tens of thousands per machine.
 
There wasn't anything else at the time. It wasn't until later when
PC graphics became competitive (circa 2000). I had a dual R10k Octane
on (well, under) my desk at SGI - sweet box, to be sure, but not cheap.
scott@slp53.sl.home (Scott Lurndal): Jul 12 02:31PM

>> compared with SMB.
 
>Superior in terms of performance, but in terms of authentication SMB was
>far superior.
 
Seriously? It was one of the most insecure protocols around.
 
>Kerberos authentication was added to NFS much later.
 
YP (later NIS after AT&T sued), was perfectly suitable and far easier
to manage centrally than what became AD.
Michael S <already5chosen@yahoo.com>: Jul 12 08:28AM -0700

On Tuesday, July 11, 2023 at 8:04:49 PM UTC+3, Scott Lurndal wrote:
> >a reasonable choice,
> So was unix and later Linux with NFS. A far superior protocol
> compared with SMB.
 
I never looked into details of NFS, but I heard sort of horror stories about it
that SMB user can't dream of in his worst nightmares.
Like mistake in the server or, may be, even particularly unfortunate combination
of mistakes on the network brings client to a halt state and the only escape
is reboot of the client.
scott@slp53.sl.home (Scott Lurndal): Jul 12 03:58PM

>> compared with SMB.
 
>I never looked into details of NFS, but I heard sort of horror stories abo=
>ut it
 
"heard". 'nuf said.
 
EDA environments almost exclusively use NIS and NFS, even today. Netapp
provides very reliable NFS servers.
 
> the only escape is reboot of the client.
 
There were some poor implementations of NFS clients (many designed to
run on Windows) which may have required rebooting clients. I've never
had that experience since RFS (the AT&T Unix remote file system later
replaced with Sun's NFS). Diskless workstations, of course, will hang
if the server stops servicing NFS requests. That's true for any network
filesystem serving a diskless client.
wij <wyniijj5@gmail.com>: Jul 11 04:56PM -0700

On Tuesday, July 11, 2023 at 5:13:59 AM UTC+8, wij wrote:
 
> > ;^)
> Thanks, it looks my class member rule win! (I can provide stronger restriction).
 
> This is one thousand bill [$1000千圓], keep the change.
 
As I am in the mood, so Appendix C is added. Updated wording are in
https://sourceforge.net/projects/cscall/files/MisFiles/ClassGuidelines.txt/download
 
+--------------------------------------------+
| Appendix C: Returning 'error' is necessary |
+--------------------------------------------+
Reusing of execution codes has two kinds, as a function or as a macro (C++
template is an advanced kind in source level). The exit points (I mean the
flowchar of machine codes, or assembly) of a function are traditionally
simplified to one point (the return address) by encoding the exit information
carried in the branch point into a return object --- the basic picture of the
original codes (the nature may be more intriguing).
So, the birth of the branch point info. carrying object and the associated cost
of space and time to encode and decode. 'error' or 'exception' is what human
thinks, it is just an information/mechanism for branching.

Control-flows between modules are similar, just have more room to play tricks.

So, libwy regards returning Errno as primitive.
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.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)