Re: Various compilers/OS/architectures calitko tests

Just a note to my 3rd comment in the previous reply:

I was thinking about that one few weeks ago, too, and even we don’t need it I think that we should add a default ctor - it won’t cost us anything. I’ve a default ctor in the Torrent/TrackerRequest/TrackerResponse private data classes and thus I don’t have to initialize private data in the Torent/… ctor bodies, code like this is fine:

[snip]

Further advantage of this approach is that private data members are initialized only once.

I forgot that this warning appears even if the default ctor exists, but not every member is initialized in it, so e.g. the Torrent::PrivateData class ctor produces these warnings…

So maybe we should initialize all members in ctors…

Regards,

Petr

Would you like to post a relpy?


This post is a reply to:
Re: Various compilers/OS/architectures calitko tests
Hi Peter, I do like the trick because if the assertion ever fails we’ll also have the message printed but we in any case will also get the filename and line (more...)

No follow-ups yet.