Monday, May 23, 2016

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

woodbrian77@gmail.com: May 23 12:07PM -0700

On Monday, May 23, 2016 at 3:01:11 AM UTC-5, David Brown wrote:
> follow-ups with stronger language. So your posts contribute
> significantly to increasing swearing in the group - probably more than
> any other individual poster.
 
Sorry if my freedom of speech bothers you. I'm free to
nag about it and you are free to nag me for nagging about it. :)
 
Brian
Ebenezer Enterprises - In G-d we trust.
http://webEbenezer.net
David Brown <david.brown@hesbynett.no>: May 23 10:39PM +0200

>> any other individual poster.
 
> Sorry if my freedom of speech bothers you. I'm free to
> nag about it and you are free to nag me for nagging about it. :)
 
Freedom of speech is a great thing (and freedom /after/ speech is even
better!). It is a shame to waste it on something so counter-productive
as your nagging. But no, I will not nag you about it - you are aware of
my opinion, and you will either act upon it or ignore it. So nagging
would not be helpful.
"Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com>: May 23 11:31PM +0200

On 23.05.2016 13:21, David Brown wrote:
>> individuals, or on groups of individuals; in their view that's impossible.
 
> The usual view of evolution is that it acts on species or groups, /not/
> on individuals.
 
I think you failed to understand what I wrote here.
 
You can get on a start on the topic, also called the evolutionary «unit
of selection» (what evolution acts on), here:
 
https://en.wikipedia.org/wiki/Unit_of_selection
 
However, the Wikipedia article, as usual, neatly avoids getting into the
issues or the raging conflicts. It yields the impression, to the casual
reader, that there is none. So I suspect that its list of examples is
also, as usual, lacking some crucial ones (I write "as usual" because,
for example, if you read Wikipedia's article on apartheid in Israel and
its section about support for the apartheid view (which the article
calls the apartheid "analogy"), you won't find a reference to the UN
resolution that equated zionism with apartheid – and it's that way all
over Wikipedia, but this is my main example).
 
[snip]
 
 
> effect at intergalactic distances, so it is best known and studied
> there. But it applies down to the space between atomic nuclei and their
> electrons.
 
You can convince yourself that a completly /uniform/ expansion is not
present, simply by considering how to measure things.
 
When everything expands at the same rate, then your ruler expands
exactly as much as everything else. So you then have no non-expanding
thing to measure the expansion against.
 
Logic, which I'm fond of. :)
 
 
[snip]
 
 
 
> Well, scientists are human too - we should not forget that. The point
> of scientific methods is to reduce the effect of personal ideas or
> convictions as we gradually enhance the body of human knowledge.
 
Yes. :)
 
 
Cheers!,
 
- Alf
David Brown <david.brown@hesbynett.no>: May 24 12:02AM +0200

On 23/05/16 23:31, Alf P. Steinbach wrote:
 
>> The usual view of evolution is that it acts on species or groups, /not/
>> on individuals.
 
> I think you failed to understand what I wrote here.
 
Yes. Having read the link below, I see now what you mean. I don't know
how right or wrong you are regarding how the majority of biologists
stand on this point - it is not something I have noticed in popular
science publications (and I am not qualified to read the expert
journals). I suppose the fact that I haven't read (or remember reading)
about such issues is circumstantial evidence for there being a consensus
of opinion.
 
> calls the apartheid "analogy"), you won't find a reference to the UN
> resolution that equated zionism with apartheid – and it's that way all
> over Wikipedia, but this is my main example).
 
Since Wikipedia pages can (for the most part) be edited by anyone,
discussions with a lot of conflict often get very messy. Often it is a
lot easier to simply agree to avoid the conflict, and present just the
agreed-on points.
 
 
> When everything expands at the same rate, then your ruler expands
> exactly as much as everything else. So you then have no non-expanding
> thing to measure the expansion against.
 
The usual ruler here is the speed of light. Perhaps the universe is not
expanding - it is light that is getting slower. Or maybe time is
slowing down.
 
In the case of galactic level expansion, we can measure the expansion
because we can use a modern ruler to view the ancient light.
 
> Logic, which I'm fond of. :)
 
Grammar, of which I am fond :-)
 
(That was, of course, an unfair tease - I am sure you can find flaws in
my English grammar, to say nothing of my Norwegian grammar.)
 
jacobnavia <jacob@jacob.remcomp.fr>: May 23 07:17PM +0200

Le 23/05/2016 à 19:11, Wouter van Ooijen a écrit :
> make your opeartor+ constexpr
Thanks but that doesn't help me further.
 
constexpr operator+(const float128_t a,const float128_t b)
{
return a+b;
}
 
At compile time then, the overloaded + operator would be called?
Wouter van Ooijen <wouter@voti.nl>: May 23 07:32PM +0200

Op 23-May-16 om 7:17 PM schreef jacobnavia:
> return a+b;
> }
 
> At compile time then, the overloaded + operator would be called?
 
When a function is declared constexpr and is called with constexpr
arguments (which literals are), it is evaluated at compile time.
 
Wouter
Marcel Mueller <news.5.maazl@spamgourmet.org>: May 23 08:04PM +0200

On 23.05.16 19.17, jacobnavia wrote:
> constexpr operator+(const float128_t a,const float128_t b)
 
> At compile time then, the overloaded + operator would be called?
 
Exactly.
 
But is up to the compiler to support this feature or not. It might do
it's work at the static initialization if it fails to evaluate the
expression at compile time for some reason.
 
 
Marcel
Paavo Helde <myfirstname@osa.pri.ee>: May 23 09:17PM +0300

On 23.05.2016 20:17, jacobnavia wrote:
> {
> return a+b;
> }
 
This is infinite recursion, you probably want to implement it somehow
otherwise.
 
> At compile time then, the overloaded + operator would be called?
 
When you use constexpr, the compiler will ensure that the function *can*
be evaluated at compile time, if passed suitable arguments. If the
function is used in a construct requiring a compile-time value (as in an
array size calculation, etc), then it will be certainly evaluated at
run-time. If it appears in some other context, then it's up to the
compiler to decide whether to evaluate it at compile time or run time
(constexpr implies inline, which is a bit similar in this sense).
 
In your case I guess you want to make sure that operator+ can be used in
compile-time expressions. This is exactly what constexpr does.
 
Cheers
Paavo
jacobnavia <jacob@jacob.remcomp.fr>: May 23 11:26PM +0200

Le 23/05/2016 à 20:17, Paavo Helde a écrit :
> compile-time expressions. This is exactly what constexpr does.
 
> Cheers
> Paavo
 
This is completely impossible. To add two float128_t I need at least
50-60% of the library to extract the components, adjust the decimal
point, do a 256 bit mantissa addition, build the result and a long etc!
 
I thought the compiler would just call a function in a dll/so or similar.
Marcel Mueller <news.5.maazl@spamgourmet.org>: May 23 11:47PM +0200

On 23.05.16 23.26, jacobnavia wrote:
> This is completely impossible. To add two float128_t I need at least
> 50-60% of the library to extract the components, adjust the decimal
> point, do a 256 bit mantissa addition, build the result and a long etc!
 
To be evaluable at compile time all functions you call need to be
constexpr. Some of the runtime function are constexpr. Some are
constexpr with platform dependent extensions. Others are not. So it depends.
 
> I thought the compiler would just call a function in a dll/so or similar.
 
No, this is impossible since the binary representations of types are not
portable in general. Note that cross compilation is not that uncommon.
 
 
Marcel
Ramine <ramine@1.1>: May 23 05:42PM -0700

Hello,
 
 
Read this paper:
 
http://www.cs.berkeley.edu/~jfc/DataMining/SP12/lecs/stochasticConjugate.pdf
 
As you have noticed in my Scalable Parallel C++ Conjugate Gradient
Linear System Solver Library i am not using a Scaling technic nor
a conditioning technic, because if you have noticed
in the scaling technic on the paper above, you have to multiply
two times a matrix by a matrix and this is expenssive,
the conditioning technic is expenssive also, and because also
my Scalable Parallel C++ Conjugate Gradient Linear System Solver
Library is scalable on NUMA architecture.
 
 
So hope you will be happy with my scalable library.
 
You can download my Scalable Parallel C++ Conjugate Gradient Linear
System Solver Library from:
 
https://sites.google.com/site/aminer68/scalable-parallel-c-conjugate-gradient-linear-system-solver-library
 
 
Thank you,
Amine Moulay Ramdane.
bleachbot <bleachbot@httrack.com>: May 23 07:15PM +0200

bleachbot <bleachbot@httrack.com>: May 23 08:00PM +0200

bleachbot <bleachbot@httrack.com>: May 23 11:41PM +0200

Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: May 23 07:49PM +0100

Amine Moulay Ramdane, fuck off.
 
/Flibble
woodbrian77@gmail.com: May 23 01:01PM -0700

On Monday, May 23, 2016 at 1:49:20 PM UTC-5,
 
Oy vey, Leigh. I agree he is goofy, but please
don't swear here.
 
Brian
Ebenezer Enterprises - "Love is patient, love is kind.
It does not envy, it does not boast, it is not proud." 1st Corinthians 13:4
 
http://webEbenezer.net
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: May 23 10:01PM +0100

> On Monday, May 23, 2016 at 1:49:20 PM UTC-5,
 
> Oy vey, Leigh. I agree he is goofy, but please
> don't swear here.
 
'This video may contain sexual swearwords, I'm afraid. There are 28
'fucks'. Including that one 29. Ah, fuck it, make it 30.' -- Paul Calf
 
https://www.youtube.com/watch?v=42UCpOzTbNU
Ramine <ramine@1.1>: May 23 02:02PM -0700

Hello...
 
My Scalable Parallel C++ Conjugate Gradient Linear System Solver Library
was updated..
 
I have just noticed that raising exceptions from inside the Dynamic Link
Libraries is not working correctly, so i have corrected this and
now i think that my library is more robust and more stable.
 
 
Please download the new updated version of my library from:
 
https://sites.google.com/site/aminer68/scalable-parallel-c-conjugate-gradient-linear-system-solver-library
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: May 23 01:15PM -0700

On 5/23/2016 12:48 PM, Ramine wrote:
 
> https://sites.google.com/site/aminer68/scalable-parallel-c-conjugate-gradient-linear-system-solver-library
 
> Thank you,
> Amine Moulay Ramdane.
 
 
Notice also, that if you give wrong method arguments, it is my Dynamic
Link Libraries implemented in Object Pascal that will catch the errors.
 
I have taken care of that.
 
 
Thank you,
Amine Moulay Ramdane.
vasuinfo1100@gmail.com: May 23 02:41AM -0700

Big Data refers to data that is too large or complex for analysis in traditional (computer files full of information) because of factors such as the (total space occupied by something), variety and speed of the data to be carefully studied. Big Data interview questions are designed for the students to understand their goals before separating and labeling the data. Topics covered are HDFS, MapReduce, Apache Hive, YARN, Sqoop, Flume, HBase, Oozie, ZooKeeper and Spark. Since the technologies are constantly changed, BigData Interview questions provides which are necessary, needed and demanded by the people to quickly upgrade their skills, to fit the needed things for BigData related jobs. If you are applying for BigData job role, it is best to answer any BigData interview questions that might come on your way. All the questions in the list were asked in real time (surrounding conditions) atleast once. We will keep on updating the list of BigData Interview questions, to suit the current industry standards.
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)