Wednesday, December 27, 2017

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

唐彬 <tb731685340@gmail.com>: Dec 27 07:50AM -0800

where can i find the code or tutorial to learn from, which can better my coding style and let me learn more about how they work?
thx a lot
woodbrian77@gmail.com: Dec 27 08:15AM -0800

On Wednesday, December 27, 2017 at 9:50:35 AM UTC-6, 唐彬 wrote:
> where can i find the code or tutorial to learn from, which can better my coding style and let me learn more about how they work?
> thx a lot
 
https://www.cprogramming.com/tutorial/c++-tutorial.html
 
A book would probably be a good idea.
 
 
Brian
Ebenezer Enterprises
http://webEbenezer.net
Paavo Helde <myfirstname@osa.pri.ee>: Dec 27 10:27PM +0200

>> where can i find the code or tutorial to learn from, which can better my coding style and let me learn more about how they work?
>> thx a lot
 
> https://www.cprogramming.com/tutorial/c++-tutorial.html
 
Congrats Brian, you have found a (hopefully rare) C++ tutorial which
seems to contain *no* mention of std::vector, std::list, etc, despite
what OP asked for!
 
It is possible to learn C++ starting from high-level containers like
std::vector and leave the legacy C pointer and raw array quirks until
later. There was a good book "Accelerated C++" doing exactly this, but
it is now a bit out-dated.
 
Some quick googling surprisingly revealed that a pretty thorough
introduction level overview can be found in wikipedia, see e.g. from
https://en.wikipedia.org/wiki/Standard_Template_Library
 
Probably there are better resources somewhere...
 
hth
Paavo
"James R. Kuyper" <jameskuyper@verizon.net>: Dec 27 03:57PM -0500

On 12/27/2017 03:27 PM, Paavo Helde wrote:
 
> Congrats Brian, you have found a (hopefully rare) C++ tutorial which
> seems to contain *no* mention of std::vector, std::list, etc, despite
> what OP asked for!
 
Go up one level: <https://www.cprogramming.com/tutorial.html> contains a
section titled "C++ Standard Template Library (STL) tutorials", with
five links underneath. I'm not, in any way, endorsing this web site.
Ian Collins <ian-news@hotmail.com>: Dec 28 10:14AM +1300

On 12/28/2017 09:57 AM, James R. Kuyper wrote:
 
> Go up one level: <https://www.cprogramming.com/tutorial.html> contains a
> section titled "C++ Standard Template Library (STL) tutorials", with
> five links underneath. I'm not, in any way, endorsing this web site.
 
Why oh why do tutorial still use that obsolete term (STL)?
 
--
Ian.
Mr Flibble <flibble@i42.co.uk>: Dec 27 09:56PM

On 27/12/2017 21:14, Ian Collins wrote:
>> section titled "C++ Standard Template Library (STL) tutorials", with
>> five links underneath. I'm not, in any way, endorsing this web site.
 
> Why oh why do tutorial still use that obsolete term (STL)?
 
To wind pedants up of course.
 
/Flibble
David Brown <david.brown@hesbynett.no>: Dec 27 09:33AM +0100

On 26/12/17 22:33, jacobnavia wrote:
 
> You can have a linux screen in a mac using vnc. Of course it runs on
> linux too, so if your linux machine is connected to the network, it
> should work.
 
vnc works as viewer and server on any "big" system (Linux, Mac, Windows,
BSD, etc.). I find it particularly useful to access Windows systems
remotely, because they don't normally have sshd and you often need a gui
for them.
 
But if you are using ssh and text mode editors like vi, why bother with
vnc? It is a lot more efficient to use ssh directly to the Linux
machines than to go via VNC. (Of course, I may be misunderstanding your
setup.)
 
 
> I have only one screen. I connect 4 machines, (a mac, a PC, and two
> small machines running on ARM/Debian) and it looks amazing to me.
 
If you have the desk space, multiple screens are worth the investment -
you can never have too many (nor too many pixels or inches).
 
 
> No games, of course. I just ned a ssh text interface for work. I still
> use vi (eclipse is too huge to try to move it to those small CPUs).
 
You can happily use eclipse on your Mac to work with files on your ARM
boards. A common setup would be to have eclipse on your "host" system
(a relatively big and fast Mac or Linux PC, or Windows if you are
willing to work much harder on the setup), and have a cross-compiler on
it. You do all your development - editing, compiling, debugging,
documentation - on that machine. Export the filesystem as NFS and mount
it on the ARM boards remotely. Then via ssh to the ARM boards, you can
run the program as though it were local to the machine. Debugging is
done with remote gdb - your host machine has the debugger gui, while the
code runs on the ARM board. It can take a little effort (and guides on
the internet) to get it all set up, but it is a lot more efficient to
work with than to do the editing and compiling on the small ARM board.
 
ram@zedat.fu-berlin.de (Stefan Ram): Dec 27 01:34AM

>I don't have a copy of clang installed, so I can't test that.
 
I have reduced the example code:
 
struct X { struct B {}; struct A { operator B(); }; };
X::A::operator B() { return B {}; }
 
. I have a clang-based style checker, which did not complain.
 
A recent draft has this example in 12.2.1p4:
 
struct X {
typedef int T;
static T count;
void f(T);
};
void X::f(T t = count) { }
 
. One can see that in the last line, »T« and »count« are
used without qualification.
 
However, in error messages, the operator function is called
 
X::A::operator X::B()
 
by gcc, hinting that this is some kind of canonical
identification of that operator function.
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: