Friday, September 30, 2016

Fwd: 转发:Dad gets a new I-Pad



Sent from my iPad


Sent from my iPad

Begin forwarded message:

From: Dolores Kuo <doloresmkuo@gmail.com>
Date: September 30, 2016 at 10:18:55 PM CDT
To: Ronny Lin <ronny_lin@hotmail.com>, Jensie Tou <pandjtou@aol.com>, chriswang_95051@yahoo.com, charlottetao1@gmail.com, 1931tao@gmail.com, nancyhychao@yahoo.com, tsoongtotherim@aol.com
Subject: Fwd: 转发:Dad gets a new I-Pad



Sent from my iPhone

Begin forwarded message:

From: "charlesmeng45_2"<charlesmeng45_2@yahoo.com>
Date: September 30, 2016 at 6:55:03 AM CDT
To: "caroline621933"<caroline621933@gmail.com>, "Dolores Gmail"<doloresmkuo@gmail.com>, "Andy Young"<Yandy48444@aol.com>, "edwin meng"<edwincmeng@gmail.com>, "scott meng"<scottmeng@hotmail.com>, "王David"<davidwang0127@gmail.com>, "楊本永"<pyyang@mail.tbcnet.net>, "Kuo Liang Yang"<kuo.liang.yang@gmail.com>, "Peter Pan"<peter281135@yahoo.com.tw>, "Sue Mong"<suemong@att.net>, "Seymour Mong "<seymour.mong@gmail.com>, "franzmong1108"<franzmong1108@yahoo.com>, "Abraham Yang"<hk1997_2001@hotmail.com>
Subject: 转发:Dad gets a new I-Pad



---原始邮件---
发件人: "patrick cheng "<pcheng77@yahoo.com>
发送时间: 2016年09月30日 01:31:36
收件人:
主题: Dad gets a new I-Pad



 

Watch the following short clip that takes less than a minute.
In fact it's only 32 seconds long.
 
A daughter is visiting her father and is helping in the kitchen.
She asks: " Tell me dad, how are you managing with the new I-Pad
we gave you for your birthday?"
 
This clip is spoken in German but it's totally understandable in any 
language.
 





Fwd: 转发:Dad gets a new I-Pad



Sent from my iPad

Begin forwarded message:

From: Dolores Kuo <doloresmkuo@gmail.com>
Date: September 30, 2016 at 10:18:55 PM CDT
To: Ronny Lin <ronny_lin@hotmail.com>, Jensie Tou <pandjtou@aol.com>, chriswang_95051@yahoo.com, charlottetao1@gmail.com, 1931tao@gmail.com, nancyhychao@yahoo.com, tsoongtotherim@aol.com
Subject: Fwd: 转发:Dad gets a new I-Pad



Sent from my iPhone

Begin forwarded message:

From: "charlesmeng45_2"<charlesmeng45_2@yahoo.com>
Date: September 30, 2016 at 6:55:03 AM CDT
To: "caroline621933"<caroline621933@gmail.com>, "Dolores Gmail"<doloresmkuo@gmail.com>, "Andy Young"<Yandy48444@aol.com>, "edwin meng"<edwincmeng@gmail.com>, "scott meng"<scottmeng@hotmail.com>, "王David"<davidwang0127@gmail.com>, "楊本永"<pyyang@mail.tbcnet.net>, "Kuo Liang Yang"<kuo.liang.yang@gmail.com>, "Peter Pan"<peter281135@yahoo.com.tw>, "Sue Mong"<suemong@att.net>, "Seymour Mong "<seymour.mong@gmail.com>, "franzmong1108"<franzmong1108@yahoo.com>, "Abraham Yang"<hk1997_2001@hotmail.com>
Subject: 转发:Dad gets a new I-Pad



---原始邮件---
发件人: "patrick cheng "<pcheng77@yahoo.com>
发送时间: 2016年09月30日 01:31:36
收件人:
主题: Dad gets a new I-Pad



 

Watch the following short clip that takes less than a minute.
In fact it's only 32 seconds long.
 
A daughter is visiting her father and is helping in the kitchen.
She asks: " Tell me dad, how are you managing with the new I-Pad
we gave you for your birthday?"
 
This clip is spoken in German but it's totally understandable in any 
language.
 





Fwd: 转发:Dad gets a new I-Pad



Sent from my iPad

Begin forwarded message:

From: Dolores Kuo <doloresmkuo@gmail.com>
Date: September 30, 2016 at 10:18:55 PM CDT
To: Ronny Lin <ronny_lin@hotmail.com>, Jensie Tou <pandjtou@aol.com>, chriswang_95051@yahoo.com, charlottetao1@gmail.com, 1931tao@gmail.com, nancyhychao@yahoo.com, tsoongtotherim@aol.com
Subject: Fwd: 转发:Dad gets a new I-Pad



Sent from my iPhone

Begin forwarded message:

From: "charlesmeng45_2"<charlesmeng45_2@yahoo.com>
Date: September 30, 2016 at 6:55:03 AM CDT
To: "caroline621933"<caroline621933@gmail.com>, "Dolores Gmail"<doloresmkuo@gmail.com>, "Andy Young"<Yandy48444@aol.com>, "edwin meng"<edwincmeng@gmail.com>, "scott meng"<scottmeng@hotmail.com>, "王David"<davidwang0127@gmail.com>, "楊本永"<pyyang@mail.tbcnet.net>, "Kuo Liang Yang"<kuo.liang.yang@gmail.com>, "Peter Pan"<peter281135@yahoo.com.tw>, "Sue Mong"<suemong@att.net>, "Seymour Mong "<seymour.mong@gmail.com>, "franzmong1108"<franzmong1108@yahoo.com>, "Abraham Yang"<hk1997_2001@hotmail.com>
Subject: 转发:Dad gets a new I-Pad



---原始邮件---
发件人: "patrick cheng "<pcheng77@yahoo.com>
发送时间: 2016年09月30日 01:31:36
收件人:
主题: Dad gets a new I-Pad



 

Watch the following short clip that takes less than a minute.
In fact it's only 32 seconds long.
 
A daughter is visiting her father and is helping in the kitchen.
She asks: " Tell me dad, how are you managing with the new I-Pad
we gave you for your birthday?"
 
This clip is spoken in German but it's totally understandable in any 
language.
 





Fwd: 🔴凌晨3:00从北京长安街传来的最新照片,惊艳全国!快打开看看!



Sent from my iPad

Begin forwarded message:

From: Peter Chang <chang737@gmail.com>
Date: September 30, 2016 at 10:20:02 PM CDT
To: "Niu, Xu Feng" <xfniu01@gmail.com>
Subject: Fwd: 🔴凌晨3:00从北京长安街传来的最新照片,惊艳全国!快打开看看!

中国,这头睡觉的狮子醒了!  还好,我还在世,有幸看到!  文井
---------- Forwarded message ----------

Date: Fri, Sep 30, 2016 at 8:17 PM
Subject: 🔴凌晨3:00从北京长安街传来的最新照片,惊艳全国!快打开看看!
To: Peter Chang <chang737@gmail.com>



http://mp.weixin.qq.com/s?__biz=MzA5OTQzNjA4NA==&mid=2650058296&idx=1&sn=c752fcdfacf861d99bddb1f4c5aefb4d&chksm=88825d63bff5d475b4686414c5af475d0036b2f86a48005818a43ad6b9a5e74251474ea56f52&mpshare=1&scene=1&srcid=0926UwjIYwZwZw7tgdvOzWMX&from=singlemessage&isappinstalled=0#wechat_redirect


发自我的 iPhone

Digest for comp.lang.c++@googlegroups.com - 12 updates in 1 topic

Paavo Helde <myfirstname@osa.pri.ee>: Sep 30 09:02AM +0300

On 30.09.2016 0:48, Richard wrote:
 
> We've already been over this in this thread, you're just repeating
> yourself here without adding any new information.
 
Yes, I'm feeling so myself too!
 
Cheers
Paavo
Robert Wessel <robertwessel2@yahoo.com>: Sep 30 02:44AM -0500

On Thu, 29 Sep 2016 00:50:59 +0200, "Alf P. Steinbach"
>that it's really about each encoding value, including those that are
>just half of surrogate pairs. That's far fetched. But since standards
>use all kinds of weird meanings of words, it can't be just dismissed.
 
 
Early versions of the Unicode standard actually included "Unicode
character codes have a uniform width of 16 bits." as one of "The Ten
Unicode Design Principles" (quotes from my hardcopy Unicode 2.0
standard - circa 1996). While also defining the surrogate pair
mechanism. The ten principles have changed since then (and the 16-bit
character thing is no longer one of them). So were Unicode characters
16 bits in those days, even in the presence of (possible) surrogate
pairs? And how does that relate to the much later C tightening of the
definition of wchar_t?
"Öö Tiib" <ootiib@hot.ee>: Sep 30 04:08AM -0700

On Wednesday, 28 September 2016 03:42:45 UTC+3, Melzzzzz wrote:
 
> Whenever one needs performance raw pointers have to be used...
> eg implementing tree structure, or linked list for that matter...
> Imagine implementing AVL tree with smart pointers ;)
 
When someone implements AVL tree for performance reasons
then he most likely keeps the nodes in some other container
(like 'vector' or 'deque') for performance reasons and so uses
the things for indexing in that container (like
'std::deque<node>::iterator' or 'std::vector<node>::size_type')
instead of 'node*' for performance reasons. ;)
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Sep 30 06:24PM +0100

On 27/09/2016 03:59, Stefan Ram wrote:
> and benchmarksgame.alioth.debian.org, and commented: C++
> is popular, but not as popular as C, and it's fast, but not
> as fast as C.
 
Nonsense, C++ is faster than C. Why? Two reasons why:
 
* C is mostly a subset of C++ and the parts that aren't have no bearing
on performance.
* C++ alternatives are often faster than their C equivalents, for
example std::sort() is faster than qsort() when passed a functor which
allows comparisons to be inlined.
 
/Flibble
Tim Rentsch <txr@alumni.caltech.edu>: Sep 30 10:52AM -0700

> Windows, wchar_t encodes individual 16-bit elements of UTF-16
> "surrogate pairs" which cannot be considered as members of any
> character set, IMHO.
 
This question came up in the newsgroup here a couple weeks ago.
Alf was kind enough to post a question on stackoverflow, which
provided some interesting and useful reading. Let me cut to the
chase. I believe the Microsoft implementation (ie, MSVC) is
technically conforming. It boils down to what characters are in
"the execution wide-character set" (this from [lex.ccon p5] in
C++14, specifically N4296, but I think there is similar wording
in C++11 and C++03). So how does the implementation define "the
execution wide-character set"? At least one source of Microsoft
documentation says this (note the part after "except"):
 
"The set of available locale names, languages,
country/region codes, and code pages includes all those
supported by the Windows NLS API except code pages that
require more than two bytes per character [...]"
 
Here is the link for that:
 
https://msdn.microsoft.com/en-us/library/x99tb11d.aspx
 
which is documentation for setlocale(), which seems pretty
definitive.
 
My conclusion is that MSVC is technically conforming, but only
weaselly conforming. They wimped out by artifically defining the
set of characters officially supported to be only those whose
code points fit in two bytes, even though the compiler obviously
knows how to deal with code points that need surrogate pairs.
Technically, they are within their rights. But they deserve to
be taken to task for running roughshod over the spirit of what
the standards (both C and C++) obviously intend.
legalize+jeeves@mail.xmission.com (Richard): Sep 30 06:00PM

[Please do not mail me a copy of your followup]
 
Tim Rentsch <txr@alumni.caltech.edu> spake the secret code
>Technically, they are within their rights. But they deserve to
>be taken to task for running roughshod over the spirit of what
>the standards (both C and C++) obviously intend.
 
Thanks for that.
 
After reading the latest messages on this thread today, I wondered
what would be the effect of wchar_t being 32-bits on Windows. My
overall conclusion is that it would be worthless.
 
- All existing code using L"" literals or wchar_t would break.
- You can't pass 32-bit wchar_t's to any Win32 APIs, you'd have to
convert to UTF-16 first and/or use char16_t everywhere instead of
wchar_t.
- The compiler could only support sizeof(wchar_t)==4 as a non-default
compiler option due to the above breakage.
- I can't think of anything useful I would do with 32-bit wchar_t on
Windows. Can anyone provide an example? It has to be other than
internal manipulation of 32-bit Unicode characters which you can
already do with char32_t.
--
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
Tim Rentsch <txr@alumni.caltech.edu>: Sep 30 11:09AM -0700

> 16 bits in those days, even in the presence of (possible) surrogate
> pairs? And how does that relate to the much later C tightening of the
> definition of wchar_t?
 
Was it that much later, or even later at all? I guess I should also ask
which tightening you are referring to. AFAIK wchar_t emerged in more or
less its current form in Amendment 1 in 1995, ie what is commonly called
C95, and has been more or less unchanged since then. Certainly wchar_t
is described in terms like those of the present day in drafts predating
C99. (In C11 the types char16_t and char32_t were added, but that seems
independent of wchar_t.)
Bo Persson <bop@gmb.dk>: Sep 30 08:23PM +0200

On 2016-09-30 19:52, Tim Rentsch wrote:
> Technically, they are within their rights. But they deserve to
> be taken to task for running roughshod over the spirit of what
> the standards (both C and C++) obviously intend.
 
What?!
 
The documentation states that you can only call the standard library
function setlocale with locales that the C and C++ standards allow.
 
The fact that the operating system happens to support additional locales
is hardly something to complain about.
 
 
Bo Persson
Paavo Helde <myfirstname@osa.pri.ee>: Oct 01 12:07AM +0300

On 30.09.2016 21:00, Richard wrote:
 
> Windows. Can anyone provide an example? It has to be other than
> internal manipulation of 32-bit Unicode characters which you can
> already do with char32_t.
 
The reality is that definition of wchar_t is platform-dependent so it
would be unwise to use it for anything intended to be portable. So the
only use I can see for wchar_t is in platform-specific code parts meant
for interfacing Windows SDK functions. char16_t is a different type so
one cannot use it for that purpose on Windows (without a lot of casting,
that is).
 
On Linux the system calls use char and UTF-8, so I have never had a need
for wchar_t there (or anything else than plain char, for that matter).
 
Cheers
Paavo
Paavo Helde <myfirstname@osa.pri.ee>: Oct 01 12:44AM +0300

On 1.10.2016 0:07, Paavo Helde wrote:
> that is).
 
> On Linux the system calls use char and UTF-8, so I have never had a need
> for wchar_t there (or anything else than plain char, for that matter).
 
I noticed that I actually did not answer the question, so in short: if
wchar_t changed to 32-bit in MSVC (with Windows SDK remaining 16-bit),
then this wchar_t would lose the single use case it had so far. OTOH, it
might now become easier to port other programs using wchar_t to Windows.
legalize+jeeves@mail.xmission.com (Richard): Sep 30 09:57PM

[Please do not mail me a copy of your followup]
 
Paavo Helde <myfirstname@osa.pri.ee> spake the secret code
>wchar_t changed to 32-bit in MSVC (with Windows SDK remaining 16-bit),
>then this wchar_t would lose the single use case it had so far. OTOH, it
>might now become easier to port other programs using wchar_t to Windows.
 
So, a huge negative impact on all existing code in return for the possible
benefit of porting some code.
--
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
Robert Wessel <robertwessel2@yahoo.com>: Sep 30 05:32PM -0500

On Fri, 30 Sep 2016 11:09:20 -0700, Tim Rentsch
>is described in terms like those of the present day in drafts predating
>C99. (In C11 the types char16_t and char32_t were added, but that seems
>independent of wchar_t.)
 
 
I don't have a copy of the C95 TC, but:
 
http://www.lysator.liu.se/c/na1.html
 
describes Unicode characters as 16 bit. The surrogate pair mechanism
was actually introduced with Unicode 2.0, and Unicode was purely a
16-bit character set in the two earlier standard versions (and in the
preceding drafts).
 
But I don't know the wording in the TC. MS used a pre-standard
version of wchar_t (which they originally typedef'd to the [16-bit]
Windows type TCHAR), way back in 1993 (and well before that if you
count the pre-release versions of WinNT).
 
So we have:
 
- Circa 1991: Unicode 1.0
- Circa 1992/1993: Unicode 1.01 and 1.1, mainly add CJK stuff
- Circa 1993: WinNT ships with (16-bit only, what we'd now call UCS-2)
Unicode 1.x support, pre-standard (16-bit) wchar_t
- Circa 1993: UTF-8 proposal made public - I'm not clear on when it
was added as a standard encoding, but it was not in unicode 1.1
(c.1993, where a earlier scheme, FSS-UTF was described), and UTF-8 was
definitely in 2.0), but there was a minor revision between those two
("1.15", c.1995), which might have added it.
- Circa 1995: TC95 standardizes wchar_t
- Circa 1995: MS Ships Win95 (first "consumer" Win32 platform) with
UCS-2 support
- Circa 1996: Unicode 2.0 adds surrogate pair support, "breaking" the
"16-bit" nature of Unicode.
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.

Digest for comp.programming.threads@googlegroups.com - 6 updates in 3 topics

Ramine <ramine@1.1>: Sep 29 11:58AM -0400

Hello.....
 
 
Google proved that it works on optimization problems and machine Leaning..
 
Google's D-Wave 2X Quantum Computer 100 Million Times Faster Than
Regular Computer Chip
 
Read more here:
 
http://www.techtimes.com/articles/114614/20151209/googles-d-wave-2x-quantum-computer-100-million-times-faster-than-regular-computer-chip.htm
 
And read this:
 
D-Wave's 2,000-Qubit Quantum Annealing Computer Now 1,000x Faster Than
Previous Generation
 
If D-Wave's 2,000-qubit computer is now 1,000 faster than the previous
1,000-qubit generation (D-Wave 2X), that would mean that, for the things
Google tested last year, it should now be 100 billion times faster than
a single-core CPU.
 
D-Wave's CEO, Vern Brownell, also said that D-Wave's quantum computers
could also be used for machine learning task in ways that wouldn't be
possible on classical computers. The company is also training the first
generation of programmers to develop applications for D-Wave quantum
systems.
 
 
Read more here:
 
http://www.tomshardware.com/news/d-wave-2000-qubit-1000x-faster,32768.html
 
 
Thank you,
Amine Moulay Ramdane. .
Ramine <ramine@1.1>: Sep 29 01:22PM -0400

On 9/29/2016 11:58 AM, Ramine wrote:
> Hello.....
 
> Google proved that it works on optimization problems and machine Leaning..
 
I mean: Machine learning, not machine leaning.
 
 
bleachbot <bleachbot@httrack.com>: Sep 29 03:29PM +0200

bleachbot <bleachbot@httrack.com>: Sep 29 05:57PM +0200

bleachbot <bleachbot@httrack.com>: Sep 29 07:21PM +0200

Ramine <ramine@1.1>: Sep 29 09:29AM -0400

Hello....
 
D-Wave's 2,000-Qubit Quantum Annealing Computer Now 1,000x Faster Than
Previous Generation
 
If D-Wave's 2,000-qubit computer is now 1,000 faster than the previous
1,000-qubit generation (D-Wave 2X), that would mean that, for the things
Google tested last year, it should now be 100 billion times faster than
a single-core CPU.
 
D-Wave's CEO, Vern Brownell, also said that D-Wave's quantum computers
could also be used for machine learning task in ways that wouldn't be
possible on classical computers. The company is also training the first
generation of programmers to develop applications for D-Wave quantum
systems.
 
 
Read more here:
 
http://www.tomshardware.com/news/d-wave-2000-qubit-1000x-faster,32768.html
 
 
Thank you,
Amine Moulay Ramdane.
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.programming.threads+unsubscribe@googlegroups.com.

Thursday, September 29, 2016

Re: 曰本

我每天看央視新聞,從未見到這麼重大事件的消息,而且兩天前也見到這網上訊息,想是極端「愛國」人士或「反中」人士為了栽贓有意誤傳!

Sent from my iPad

On Sep 29, 2016, at 5:57 PM, Tina Soong <tinasoong@att.net> wrote:



Sent from my iPad


Sent from my iPad

Begin forwarded message:

From: Frank Yen <yen401k@gmail.com>
Date: September 29, 2016 at 1:32:18 PM CDT
To: "Frank T. Yen" <yen401k@gmail.com>
Subject: Fwd: Fw: Fwd: 曰本




-------- Forwarded Message --------
Subject: Fw: Fwd: 曰本
Date: Thu, 29 Sep 2016 18:25:40 +0000 (UTC)
From: hai-tan tu <htu1953@yahoo.com>
Reply-To: hai-tan tu <htu1953@yahoo.com>
To: Frank Yen <yen401k@gmail.com>





Dear All,
此篇乃我高中同學,曾任蔣孝嚴主秘所傳!今日臺灣政府媚日,如果全球華人均對日本安倍以實際行動治裁, 一如今日臺灣對綠營執政反彈!則首先令日本業者反思,令安倍後悔為二戰造下之罪孽道歉!蔡英文亦失卻靠山!如果我們人人發自內心,去為全球中華民族一吐往年怨氣!只要我們每日做到不去給日本人再佔一點便利,且我們才可以為被日本軍閥在二戰時,殘殺數千萬之英靈平反!唯有滅了安倍和蔡英文的不可一世威風,才能維持世界和平!我們才會有安樂日子過也!

Sent from my iPad

Begin forwarded message:

From: Lin Chao <alphazl2000@gmail.com>
Date: September 28, 2016 11:12:15 PM PDT
To: ShiuePH薛平華 <joseph@phins.co>, 李 Lee 震坤 Jack K.Q. <jacklee0116@hotmail.com>, Paul Hsu <p.hsu46@gmail.com>
Subject: Fwd: 曰本



Fwd: 曰本



Sent from my iPad


Sent from my iPad

Begin forwarded message:

From: Frank Yen <yen401k@gmail.com>
Date: September 29, 2016 at 1:32:18 PM CDT
To: "Frank T. Yen" <yen401k@gmail.com>
Subject: Fwd: Fw: Fwd: 曰本




-------- Forwarded Message --------
Subject: Fw: Fwd: 曰本
Date: Thu, 29 Sep 2016 18:25:40 +0000 (UTC)
From: hai-tan tu <htu1953@yahoo.com>
Reply-To: hai-tan tu <htu1953@yahoo.com>
To: Frank Yen <yen401k@gmail.com>





Dear All,
此篇乃我高中同學,曾任蔣孝嚴主秘所傳!今日臺灣政府媚日,如果全球華人均對日本安倍以實際行動治裁, 一如今日臺灣對綠營執政反彈!則首先令日本業者反思,令安倍後悔為二戰造下之罪孽道歉!蔡英文亦失卻靠山!如果我們人人發自內心,去為全球中華民族一吐往年怨氣!只要我們每日做到不去給日本人再佔一點便利,且我們才可以為被日本軍閥在二戰時,殘殺數千萬之英靈平反!唯有滅了安倍和蔡英文的不可一世威風,才能維持世界和平!我們才會有安樂日子過也!

Sent from my iPad

Begin forwarded message:

From: Lin Chao <alphazl2000@gmail.com>
Date: September 28, 2016 11:12:15 PM PDT
To: ShiuePH薛平華 <joseph@phins.co>, 李 Lee 震坤 Jack K.Q. <jacklee0116@hotmail.com>, Paul Hsu <p.hsu46@gmail.com>
Subject: Fwd: 曰本



Fwd: 曰本



Sent from my iPad

Begin forwarded message:

From: Frank Yen <yen401k@gmail.com>
Date: September 29, 2016 at 1:32:18 PM CDT
To: "Frank T. Yen" <yen401k@gmail.com>
Subject: Fwd: Fw: Fwd: 曰本




-------- Forwarded Message --------
Subject: Fw: Fwd: 曰本
Date: Thu, 29 Sep 2016 18:25:40 +0000 (UTC)
From: hai-tan tu <htu1953@yahoo.com>
Reply-To: hai-tan tu <htu1953@yahoo.com>
To: Frank Yen <yen401k@gmail.com>





Dear All,
此篇乃我高中同學,曾任蔣孝嚴主秘所傳!今日臺灣政府媚日,如果全球華人均對日本安倍以實際行動治裁, 一如今日臺灣對綠營執政反彈!則首先令日本業者反思,令安倍後悔為二戰造下之罪孽道歉!蔡英文亦失卻靠山!如果我們人人發自內心,去為全球中華民族一吐往年怨氣!只要我們每日做到不去給日本人再佔一點便利,且我們才可以為被日本軍閥在二戰時,殘殺數千萬之英靈平反!唯有滅了安倍和蔡英文的不可一世威風,才能維持世界和平!我們才會有安樂日子過也!

Sent from my iPad

Begin forwarded message:

From: Lin Chao <alphazl2000@gmail.com>
Date: September 28, 2016 11:12:15 PM PDT
To: ShiuePH薛平華 <joseph@phins.co>, 李 Lee 震坤 Jack K.Q. <jacklee0116@hotmail.com>, Paul Hsu <p.hsu46@gmail.com>
Subject: Fwd: 曰本



Tuesday, September 27, 2016

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

Real Troll <real.troll@trolls.com>: Sep 26 01:50PM -0400

On 26/09/2016 18:27, Richard wrote:
 
> Hmm. Seems like all these bible thumping assholes that insist on
> ruining this newsgroup have most of these characteristics.
 
And you are aiding and abetting them to do just that!!
Juha Nieminen <nospam@thanks.invalid>: Sep 27 06:16AM


>> Hmm. Seems like all these bible thumping assholes that insist on
>> ruining this newsgroup have most of these characteristics.
 
> And you are aiding and abetting them to do just that!!
 
How, exactly? The thread already exists. Writing to it isn't going
to change anything.
 
--- news://freenews.netfront.net/ - complaints: news@netfront.net ---
Juha Nieminen <nospam@thanks.invalid>: Sep 27 06:17AM

> Being good isn't enough. Being great isn't enough. Being the best person
> you can possibly be isn't enough.
 
Yeah, being a self-righteous hypocritical asshole is much better, you
retarded narcissistic imbecile.
 
--- news://freenews.netfront.net/ - complaints: news@netfront.net ---
"Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Sep 27 03:45AM -0700

Juha Nieminen wrote:
> [snip]
 
Come to Him and ask Him to forgive your multitude of sins.
He will forgive every last one, no matter what you've done or to
whom. He has the power, authority, and desire to forgive you. He's
> only waiting for you to come to Him and ask for forgiveness. I
> pray you do. I would like to see you in Heaven.
 
-----
Each of us should pay special attention to how we regard God in
our hearts.
 
http://biblehub.com/kjv/revelation/22.htm
10 And he saith unto me, Seal not the sayings of the prophecy of
this book: for the time is at hand.
11 He that is unjust, let him be unjust still: and he which is
filthy, let him be filthy still: and he that is righteous, let him
be righteous still: and he that is holy, let him be holy still.
 
12 And, behold, I come quickly; and my reward is with me,
to give every man according as his work shall be.
13 I am Alpha and Omega, the beginning and the end, the first
and the last.
 
14 Blessed are they that do his commandments, that they
may have right to the tree of life, and may enter in through the
gates into the city.
15 For without are dogs, and sorcerers, and whoremongers, and
murderers, and idolaters, and whosoever loveth and maketh
a lie.
 
He is giving each of us there in Revelation 22:11-12 the opportunity
to reveal unto God for ourselves who we are, so that it will not be
He who condemns a person to Hell, but the person themselves
by the full revelation of their character, their substance, and their
being before God (who has made Himself known in countless ways
before their eyes, hearts, and minds).
 
-----
I point you to truth, Juha. It is not my creation, but is of God. I do
not hold exclusive rights or access to this information. It's why
I teach you, so that you can possess it too and teach others, for
once you taste of the Lord ... you can do no other. He's that
amazing, that enthralling, that astounding, and He's unlike other
things. He's a leader, and He makes us His by His wonderful,
marvelous attributes and deeds.
 
I pray you come to know Him. I would like to see you in Heaven.
 
Best regards,
Rick C. Hodgin
Real Troll <real.troll@trolls.com>: Sep 27 01:45PM -0400

On 27/09/2016 07:16, Juha Nieminen wrote:
> How, exactly? The thread already exists. Writing to it isn't going
> to change anything.
 
Responding to Rick C Idiot is going to change everything. Best thing is
to ignore him and some would even filter him out so that no reply his
posted by mistake. He is someone who thinks that Jesus Christ has given
him the right to spam these newsgroups.
Lynn McGuire <lynnmcguire5@gmail.com>: Sep 26 09:43PM -0500

"2 major reasons why modern C++ is a performance beast"
https://www.oreilly.com/ideas/2-major-reasons-why-modern-c-is-a-performance-beast
 
"The Prime Directive in the C/C++ continuum has always been performance. As I often tell groups when teaching C++, when I ask a
question beginning with "Why" concerning the rationale for a particular C++ language or library feature, they have a 90% chance of
getting the answer right by replying with a single word: "Performance.""
 
Yup.
 
Lynn
woodbrian77@gmail.com: Sep 26 08:14PM -0700

On Monday, September 26, 2016 at 9:43:26 PM UTC-5, Lynn McGuire wrote:
> question beginning with "Why" concerning the rationale for a particular C++ language or library feature, they have a 90% chance of
> getting the answer right by replying with a single word: "Performance.""
 
> Yup.
 
He makes some good points, but he claims there's no more
need for raw pointers as of C++ 2014. Oy vey. Raw pointers
are still needed, but not as much as in the past.
 
 
Brian
Ebenezer Enterprises - In G-d we trust.
http://webEbenezer.net
"Öö Tiib" <ootiib@hot.ee>: Sep 27 03:53AM -0700


> He makes some good points, but he claims there's no more
> need for raw pointers as of C++ 2014. Oy vey. Raw pointers
> are still needed, but not as much as in the past.
 
He seems correct. There are no need to use raw pointers in C++.
We may want to use those for legacy reasons, for convenience
or for optimizing something. For about same reason we may want
to use inline assembler. It felt already like that with C++2003
plus boost library.
 
For example the three (most prominent IMHO) raw pointer
usages:
* 'main' can have raw pointer argument;
* for covariant return;
* for interfacing with other programming languages.
 
Can any of those really described as a "need"? Can you
name some more important cases?
Ben Bacarisse <ben.usenet@bsb.me.uk>: Sep 27 02:54PM +0100

>> On Monday, September 26, 2016 at 9:43:26 PM UTC-5, Lynn McGuire wrote:
>> > "2 major reasons why modern C++ is a performance beast"
>> > https://www.oreilly.com/ideas/2-major-reasons-why-modern-c-is-a-performance-beast
<snip>
> * for interfacing with other programming languages.
 
> Can any of those really described as a "need"? Can you
> name some more important cases?
 
I suppose it depends on what constitutes "use" or "need". C++ string
literals convert to raw pointers, so
 
std::string greeting("Hello world");
 
"needs" raw pointers in some sense.
 
--
Ben.
Melzzzzz <Melzzzzz@zzzzz.com>: Sep 27 01:56PM

> or for optimizing something. For about same reason we may want
> to use inline assembler. It felt already like that with C++2003
> plus boost library.
 
Hm, what about filling mmaped framebuffer? Or doing ray tracing?
There are a lot more, but these examples came first to me...
 
 
--
press any key to continue or any other to quit
woodbrian77@gmail.com: Sep 27 09:43AM -0700

On Tuesday, September 27, 2016 at 5:54:25 AM UTC-5, Öö Tiib wrote:
> * for interfacing with other programming languages.
 
> Can any of those really described as a "need"? Can you
> name some more important cases?
 

Most containers and smart pointer classes use raw pointers.
 
constexpr basic_string_view(const CharT* s, size_type count);
 
Application programmers don't have to use raw pointers as
much as in the past, but raw pointers are an important part
of the language. The author of that article says there's
no more need for raw pointers "in the language."
 
 
Brian
Ebenezer Enterprises
http://webEbenezer.net
"Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com>: Sep 27 06:58PM +0200

On 27.09.2016 12:53, Öö Tiib wrote:
 
>> He makes some good points, but he claims there's no more
>> need for raw pointers as of C++ 2014. Oy vey. Raw pointers
>> are still needed, but not as much as in the past.
 
The author conflates use of pointers with ownership, presumably because
that's what he feels is important. One could start taking him seriously
if he pointed out the ownership issue as such, but he doesn't. He just
conflates.
 
 
> * for covariant return;
> * for interfacing with other programming languages.
 
> Can any of those really described as a "need"?
 
Yes, the last point.
 
The arguments of `main` are not really needed because they're a
non-portable solution for what they were designed for, namely to be able
to handle command line arguments that include file names. In order to
write portable code that also works in Windows, they can't be used for
that purpose. So they're only useful for learners and in Unix-land.
 
Covariant returns are not needed because it's trivial to implement
covariant returns, and because that has to be done anyway with non-raw
type, albeit with some code size overhead.
 
 
> Can you name some more important cases?
 
Raw pointers are good for referring to objects without carrying ownership.
 
And yes, practitioners need that.
 
It would be extraordinarily inefficient & verbose, i.e. extremely silly,
to use e.g. `std::weak_ptr` for such references.
 
More generally, practitioners need clean tools that are designed for a
single purpose. A smart pointer can't be easily divided into its
constituent responsibilities: ownership management, and reference. When
you need one without the other, you can't easily use a smart pointer.
 
Raw pointers are also good for referring to functions. They're
reseatable (assignable). References are much more cumbersome for this.
 
Cheers, & hth.,
 
- Alf
scott@slp53.sl.home (Scott Lurndal): Sep 27 05:09PM

> But I believe that it is simpler to always use C++ string
> literals than to sometimes use C string literals and
> sometimes C++ string literals.
 
Do you actually write programs that do something useful, or
do you just teach?
scott@slp53.sl.home (Scott Lurndal): Sep 27 05:11PM

>to handle command line arguments that include file names. In order to
>write portable code that also works in Windows, they can't be used for
>that purpose. So they're only useful for learners and in Unix-land.
 
Fortunately, a large fraction of C++ code never needs to run on
Windows. Thankfully.
ram@zedat.fu-berlin.de (Stefan Ram): Sep 26 11:34PM

>Not sure exactly what you're quoting here or what you're asking for
>rationale about, can you clarify?
 
The rationale for the apparent guideline to write
 
const int i = 2;
 
instead of
 
int const i = 2;
 
. I was quoting the Library Design Guidelines
(Standard Library Guidelines) from isocpp.org.
ram@zedat.fu-berlin.de (Stefan Ram): Sep 27 12:25AM

>this regard MSVC is correct and GCC (as I said before)
>"doesn't make any sense". Hence, my question -- what happens
>here? Is it allowed under C++ standard?
 
I believe that I now might have actually understood your
question, but I have no answer yet.
 
But while reading about the subject, I came along this from
12.8p15 of C++03:
 
»when a temporary class object that has not been bound
to a reference (12.2) would be copied to a class object
with the same cv-unqualified type, the copy operation
can be omitted by constructing the temporary object
directly into the target of the omitted copy«.
 
However, I cannot find this wording in a recent draft!
(The corresponding location might be 12.8p31.)
 
Possibly, I was able to simplify your source code somewhat
as follows:
 
main.cpp
 
#include <iostream>
#include <ostream>
 
struct H
{ H() { ::std::cout << "+\n"; }
~H() { ::std::cout << "-\n"; }
H( H const & ) {}};
 
int g( H h ){ return 0; }
int log( int ){ ::std::cout << "returned from g.\n"; return 0; }
int main(){ log( g( H() )); }
 
transcript
 
+
returned from g.
-
 
Now, we might be able to say that you would prefer the output:
 
+
-
returned from g.
 
because the object »h« should be destroyed when the
incarnation of the function »g« ends and not later.
ram@zedat.fu-berlin.de (Stefan Ram): Sep 27 02:59AM

>for a particular C++ language or library feature, they have a
>90% chance of getting the answer right by replying with a
>single word: "Performance.""
 
Recently, while teaching C++, I showed statistics from TIOBE
and benchmarksgame.alioth.debian.org, and commented: C++
is popular, but not as popular as C, and it's fast, but not
as fast as C.
 
"My queen, you are the fairest here so true.
But Snow White beyond the mountains at the
seven dwarfs is a thousand times more beautiful
than you."
ram@zedat.fu-berlin.de (Stefan Ram): Sep 27 03:50PM

>directly into the target of the omitted copy«.
 
>However, I cannot find this wording in a recent draft!
>(The corresponding location might be 12.8p31.)
 
It is possible that 8.6p17.6.1 now holds a similar
requirement:
 
»If the initializer expression is a prvalue and the
cv-unqualified version of the source type is the same
class as the class of the destination, the initializer
expression is used to initialize the destination object.
[ Example: T x = T(T(T())); calls the T default
constructor to initialize x. - end example ]«.
ram@zedat.fu-berlin.de (Stefan Ram): Sep 27 03:59PM

>literals convert to raw pointers, so
> std::string greeting("Hello world");
>"needs" raw pointers in some sense.
 
In my course I now call such string literals
"C string literals" as opposed to the C++ string
literals I am using throughout, as in:
 
main.cpp
 
#include <iostream>
#include <ostream>
#include <string>
 
using namespace ::std::literals;
 
int main() { ::std::cout << "Hallo, Welt"s << "\n"s; }
 
transcript
 
Hallo, Welt
 
Using »s« above does not simplify things, far from it!
But I believe that it is simpler to always use C++ string
literals than to sometimes use C string literals and
sometimes C++ string literals.
"Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Sep 27 08:26AM -0700

What did Jesus suffer in our place upon the cross? And why?
 
Beaten:
https://www.youtube.com/watch?v=d8BQKEmvKvA
 
Nailed to a cross, hung to die:
https://www.youtube.com/watch?v=PYHQuayhMeU
 
And when He gave up the Ghost, an Earthquake:
https://www.youtube.com/watch?v=njUlc2QP_7k&t=1m11s
 
Resurrection:
https://www.youtube.com/watch?v=j2Mnsxj2N7Y&t=0m11s
 
It is generally accepted that the beating shown in the movie The Passion of
The Christ, albeit very graphic, is insufficient. He was regarded as being
hung upon the cross in a form "unrecognizable as a man.". Cut and maimed so
badly, beaten to the core with his bones poking through, his muscles torn.
 
Psalm 22 speaks of some of this:
 
http://biblehub.com/kjv/psalms/22.htm
 
14 I am poured out like water, and all my bones are out of joint: my
heart is like wax; it is melted in the midst of my bowels.
 
15 My strength is dried up like a potsherd; and my tongue cleaveth to
my jaws; and thou hast brought me into the dust of death.
 
16 For dogs have compassed me: the assembly of the wicked have inclosed
me: they pierced my hands and my feet.
 
17 I may tell all my bones: they look and stare upon me.
 
He took all of this to set us free from the punishment of sin. And what
we see here on the Earth is only what happened in the flesh. What then
happened to Him in Hell when God the Father poured out His wrath full
strength upon His Son for ALL of the sin of ALL the believers, past,
present, and future ... the Bible records it literally crushed Him.
 
We haven't seen that part on this side of the grave. But it was far
worse than He endured here upon the Earth. The pouring out of punishment
literally crushed God. And such a punishment awaits all who don't find
salvation in Jesus Christ. And there's no coming back from that degree
of punishment by anyone ... except the One who's already come back, the
One who reaches out to save you right now today, so that you might live
and not receive that punishment, being set free by His blood, by His love,
by His free offer of salvation.
 
He stands with His arms out waiting for you to come to Him. I pray you
do. You have tremendous value and I would like to see you in Heaven.
 
-----
If you've never seen the Passion of the Christ, it conveys the story of the
last days on Earth for Jesus, the passion. It covers some of His teaching
in the time before, the triumphant entry into Jerusalem, His betrayal, the
mock trial where they found no fault in Him, and the sentence of Pontius
Pilate who condemned Him to death by crucifixion even though he found no
fault in Him, but Pilate was afraid of an uprising and even more bloodshed,
so He condemned an innocent man to keep the peace, as it were.
 
You can read about the story in the Bible:
 
Matthew 26:36+
http://biblehub.com/kjv/matthew/26.htm#36
 
Mark 14:32+
http://biblehub.com/kjv/mark/14.htm#32
 
Luke 22:39+
http://biblehub.com/kjv/luke/22.htm#39
 
John 18:1+
http://biblehub.com/kjv/john/18.htm
 
-----
Some key passages:
 
Luke 23:23-24 -- The sentence of death by crucifixion
23 And [the crowd was] instant with loud voices, requiring that he
might be crucified. And the voices of them and of the chief
priests [the Jewish authority] prevailed.
24 And Pilate gave sentence that it should be as they required.
 
Luke 23:44-46 -- The death
44 And it was about the sixth hour, and there was a darkness over
all the earth until the ninth hour.
45 And the sun was darkened, and the veil of the temple was rent
in the midst.
46 And when Jesus had cried with a loud voice, he said, Father,
into thy hands I commend my spirit: and having said thus,
he gave up the ghost.
 
Luke 23:52-53 -- The burial
52 This man [Joseph of Arimathaea] went unto Pilate, and begged
the body of Jesus.
53 And he took it down, and wrapped it in linen, and laid it in
a sepulchre that was hewn in stone, wherein never man before
was laid.
 
Luke 24:1-7 -- The Resurrection
1 Now upon the first day of the week, very early in the morning,
they came unto the sepulchre, bringing the spices which they
had prepared, and certain others with them.
2 And they found the stone rolled away from the sepulchre.
3 And they entered in, and found not the body of the Lord Jesus.
4 And it came to pass, as they were much perplexed thereabout,
behold, two men stood by them in shining garments:
5 And as they were afraid, and bowed down their faces to the earth,
they said unto them, Why seek ye the living among the dead?
6 He is not here, but is risen: remember how he spake unto you when
he was yet in Galilee,
7 Saying, The Son of man must be delivered into the hands of sinful
men, and be crucified, and the third day rise again.
 
-----
The Passion of the Christ movie is available at your local movie rental
place, and online for purchase or viewing. Netflix periodically has it
for viewing, but right now it's on Netflix DVD-only.
 
The Bible teaches us that "Faith comes by hearing, and hearing by the
word of God" (http://biblehub.com/kjv/romans/10-17.htm).
 
If your faith is weak, read the Bible. The words of the Bible are His
words, penned by men through the power and guidance of His Holy Spirit.
The words of the Bible are alive and active and they will increase one's
faith, and lead the truth seeker into knowledge of the truth, as much as
they're able to receive.
 
But for the one not seeking the truth, it will forever be a veiled enigma
that seems undecipherable, unintelligible, unbelievable, and a book to be
mocked and poked fun at, along with all those who believe in the One the
book speaks about, Jesus Christ.
 
It is that way because of the division between the born again nature,
and the natural man. The two are irreconcilable, and they are polar
opposites. The natural man cannot receive the things of God, and the
born again person cannot continue for long in the things of man, for
the ways of God are far greater, as they lead to life, life eternal,
and life more abundant.
 
Best regards,
Rick C. Hodgin
infocim249@gmail.com: Sep 27 02:28AM -0700

Big data is a term that describes the large volume of data which has both structured and unstructured that overloads a business on a day-to-day basis. Big Data Analyst Training It's not the amount of data that's important, It's how the companies handle the data that matters the most. A big data analyst needs/demands a different skill sets and abilities and in general a big data analyst's next step can be that of a big data scientist. A big data analyst needs to be able to support the business and management with clear and intelligent analyses on the data (nearby/ close/ currently important). Nowadays, this is no wonder that IT professionals are looking for ways to cash in on this rich vein of job opportunity.
"Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Sep 27 03:51AM -0700

This YouTube channel covers many HPC topics, including big data:
 
https://www.youtube.com/user/RichReport
 
A few months back there was a video about a company in
Australia mandated to maintain information on various species
of insects and other life. They were over $1 billion a year IIRC,
and a huge data footprint.
 
An interesting presentation.
 
Best regards,
Rick C. Hodgin
"Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Sep 27 05:19AM -0700

On Tuesday, September 27, 2016 at 6:51:25 AM UTC-4, Rick C. Hodgin wrote:
> of insects and other life. They were over $1 billion a year IIRC,
> and a huge data footprint.
 
> An interesting presentation.
 
Found it:
 
"A Journey to a Holistic Framework for Data-intensive Workflows"
Ian Corner, CSIRO
 
https://www.youtube.com/watch?v=x7Yxf1l3Kx0
 
Best regards,
Rick C. Hodgin
"Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com>: Sep 27 05:31AM +0200

On 27.09.2016 01:34, Stefan Ram wrote:
 
> int const i = 2;
 
> . I was quoting the Library Design Guidelines
> (Standard Library Guidelines) from isocpp.org.
 
Oh, I understand. Sorry.
 
Well, standard library work has to follow the conventions already
established for the C++ standard. It would be just too much work to
change those conventions now. So that's a very direct rationale.
 
I read "the wrong place" as an acknowledgment that the original choice,
back in the 1990's, was sub-optimal.
 
But, in modern C++ we don't have to cater to the idiosyncracies of the C
declaration syntax.
 
We can just define a `Ptr_` type builder, and a `Ref_`, and so on.
 
• • •
 
At first, years ago, I went all the way and also defined `Const_`.
 
But it's silly to define a new syntax where the current one works.
 
I found it useful to define a `With_const_like_`, in order to transfer
constness from one type to another. But I'm still searching for a
better, shorter name for that.
 
• • •
 
There is also a more radical idea of defining `const` versions of all
the basic types and require use of e.g. `Var_` to make something
mutable. I don't think this idea can be made practically workable: the
confusion would be akin to redefining `+` as `-`. But with this idea
 
Ptr_<Int> p;
 
would not compile, because it would declare an uninitialized `int const*
const`.
 
One would have write e.g.
 
Var_<Ptr_<Int_>> p;
 
to get something mutable.
 
Or
 
Ptr_<Var_<Int>> p = &blah;
 
:)
 
 
Cheers!,
 
- Alf
Gareth Owen <gwowen@gmail.com>: Sep 27 06:51AM +0100


> It was possibly in this newsgroup where the topic
> "const T vs T const" was discussed some months ago.
> (Or it might have been "comp.lang.c".)
 
As an equally vital followup, how many angels can we fit on the head of
a pin?
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.