Monday, February 23, 2015

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

Ramine <ramine@1.1>: Feb 23 03:45PM -0800

Hello,
 
I was thinking more, and i have noticed that you haven't agreed with
me that my parallel varfiler can be called an invention... and that
other of my programming projects are inventions too, but anyway my
inventions have to be judged on the critera of "quality" i think, and
speaking about software "quality", i have to define what's the
"criterions" that allow us to judge software quality, we have the
following criterons that permit us to judge software quality:
 
- Reliability
- Efficiency
- Security
- Maintainability
- Identifying critical programming errors
- and portability
- expressivness
 
But i have to be frank with you, what i have found difficult is when
only one individual must fulfill the goal alone of attaining a high
level degree of software quality , i mean when you are implementing a
programming project alone , you have to take into account all the above
criteria alone, and to fullfil the most important goal of programming
that is a high degree of "quality" alone... but when you are working in
a team , the manager of the team has to divide the work efficiently
between members of the team so that each one have not to take into
account all the above criteria alone, but has to fullfil this goal only
for some of the above criterions, so that programming becomes much
easier and efficient, this is what i have tried to achieve alone by
implementing my parallel varfiler, so the question is then: does my
parallel varfiler fulfill this goal of a high degree of software quality
? i think that my parallel varfiler is good, cause on the criterion of
reliability it is good, cause it is stable and it is even fault tolerant
to power failures, and to "disk full" errors etc.
and on the criterion of efficiency it is good also, because it is fast
and efficient, and on the criterion of maintainability, it is good also,
because it is easy to maintain, and on the criteria of expressivness it
is good also, cause my parallel varfiler is
a parallel hashtable that works from the memory and it can also work
from memory and from the hardisk, and you can easily save manually the
parallel hashtable to a hardisk's file, or you can configure parallel
varfiler to save "automaticly" your keys and corresponding datas to a
hardisk's file at realtime, i mean when you call update() or delete() or
add()... it can do it at realtime on memory and on the hardisk's file,
and my parallel varfiler is a parallel hashtable that uses lock striping
so it is good... and on the portability criterion my parallel varfiler
is portable to other operating systems such us windows, linux and MacOSX
on x86 systems. This is why i have told you that you will not find this
concept that i have designed and called parallel varfiler
on C++ and C# or Java, if you are not convinced , can you show me
were my parallel varfiler has been implemented on C++ or C# or Java ?
so this is why i have told you that my parallel varfiler is a good
candidate to be called an invention, and i think that my other projects
such us my parallel conjugate gradient linear system solver library that
is cache-aware and scalable on NUMA architecture, and my other projects
and inventions too , are good also...
 
 
You can download my projects from here:
 
https://sites.google.com/site/aminer68/
 
 
 
Thank you for your time.
 
 
Amine Moulay Ramdane.
Chris Vine <chris@cvine--nospam--.freeserve.co.uk>: Feb 23 09:16PM

On Mon, 23 Feb 2015 15:45:45 -0800
Ramine <ramine@1.1> wrote:
[snip lots of rubbish]
 
You said in your post entitled "That was my last post here in this
forum" that you were not going to post to this newsgroup. (It is a
newsgroup by the way, not a "forum".)
 
Please stick to what you said. This is a C++ newsgroup. Your posts
have had nothing to do with C++. You are an egocentric, self-obsessed
pest, probably a manic-depressive, who thinks everyone wants to read
your utterances as if the newsgroup were your private blog.
 
However, this is not your private blog. Go away.
Bonita Montero <Bonita.Montero@gmail.com>: Feb 23 10:28PM +0100

Chris Vine wrote:
 
> ..., probably a manic-depressive, ...
 
At least manic - that's what I also thought.
Manic people often have a communicativeness that completely
ignores their social environment.
Ramine <ramine@1.1>: Feb 23 04:19PM -0800

Hello,
 
 
My post titled "Software quality and programming" was my last post here
in this forum.
 
 
Thank you,
Amine Moulay Ramdane.
Nobody <nobody@nowhere.invalid>: Feb 23 12:24AM

On Sat, 21 Feb 2015 16:09:41 +0000, JiiPee wrote:
 
 
>> /Flibble
 
> Yes like this maybe in non-Windows programming. But.... you know Windows
> uses UTF-16
 
Windows uses arrays of wchar_t. Whether those represent UTF-16 or UCS-2
is ... underspecified to say the least. In practical terms, if the data
contains any surrogates, all bets are off.
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Feb 23 12:25AM

On 23/02/2015 00:24, Nobody wrote:
 
> Windows uses arrays of wchar_t. Whether those represent UTF-16 or UCS-2
> is ... underspecified to say the least. In practical terms, if the data
> contains any surrogates, all bets are off.
 
Windows fully supports surrogate pairs.
 
/Flibble
Robert Wessel <robertwessel2@yahoo.com>: Feb 23 02:12AM -0600

On Mon, 23 Feb 2015 00:25:29 +0000, Mr Flibble
>> is ... underspecified to say the least. In practical terms, if the data
>> contains any surrogates, all bets are off.
 
>Windows fully supports surrogate pairs.
 
 
FSVO "fully". Everything in the box may now fully support surrogates,
but it wasn't that long ago some ancillary bits (notepad, for
example), didn't. But there is much Windows software that does not.
Christopher Pisz <nospam@notanaddress.com>: Feb 23 10:25AM -0600

On 2/21/2015 12:23 PM, JiiPee wrote:
 
>> /Flibble
 
> I read that Qt does not have anymore support properly as the old company
> who supported it stopped supporting it....
 
 
To create any new software using MFC is idiocy.
To create new UI targeting Windows only, using any C++ framework is also
retarded.
 
Use .NET and WPF, or a web client. Get your UI done in 1/200th of the
time. This is what every company targeting Windows that I've worked at
for the last 5 years has done.
 
You don't need a high performance, low level control language to wait an
eon for a user to press a button.
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Feb 23 05:24PM

On 23/02/2015 16:25, Christopher Pisz wrote:
> for the last 5 years has done.
 
> You don't need a high performance, low level control language to wait an
> eon for a user to press a button.
 
More bullshit mate, you really ought to try harder. Just because you
are *currently* targeting Windows doesn't mean you shouldn't use a
cross-platform GUI framework. Why? One word: flexibility.
 
/Flibble
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Feb 23 05:25PM

On 23/02/2015 08:12, Robert Wessel wrote:
 
> FSVO "fully". Everything in the box may now fully support surrogates,
> but it wasn't that long ago some ancillary bits (notepad, for
> example), didn't. But there is much Windows software that does not.
 
Windows and software that runs on Windows are not the same thing mate.
 
/Flibble
Christopher Pisz <nospam@notanaddress.com>: Feb 23 01:05PM -0600

On 2/23/2015 11:24 AM, Mr Flibble wrote:
> are *currently* targeting Windows doesn't mean you shouldn't use a
> cross-platform GUI framework. Why? One word: flexibility.
 
> /Flibble
 
Is cross platform a religion of yours?
 
Employers just love paying for months of man hours to support other
platforms they told you up front they will never target...
 
I'm sure everyone you work with would also love to review and maintain
5000 lines of code that accomplishes what XAML will in 10.
Chris Vine <chris@cvine--nospam--.freeserve.co.uk>: Feb 23 08:38PM

On Mon, 23 Feb 2015 13:05:20 -0600
> On 2/23/2015 11:24 AM, Mr Flibble wrote:
> > On 23/02/2015 16:25, Christopher Pisz wrote:
[snip]
> platforms they told you up front they will never target...
 
> I'm sure everyone you work with would also love to review and
> maintain 5000 lines of code that accomplishes what XAML will in 10.
 
I think you looking at this the wrong way around, perhaps to be
contentious and make one of your sometimes (but not always) misaligned
points.
 
You choose C++ for a program because it fits the problem domain
(primarily, efficiency). If the program happens to have a GUI
interface, it is of secondary importance. If it happens to use a
GUI, you choose whatever seems best to you at the time, of which there
are several options.
 
If a program has such a complex GUI interface that programming it in
C++ is a significant impediment to a return on investment, it is
probably not a program where C++ is the correct solution to begin
with. So you are writing a piece of consumer krapware which you chuck
out as fast as you can? Then by all means use .NET, C# and XAML[1]. (I
like C# by the way, it is good for some things which don't have a
complex GUI and are not krapware also.)
 
Chris
 
[1] Qt, GTK+ (and so wxWidgets) and no doubt other toolkits have their
own version of XAML (QML and GtkBuilder respectively).
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Feb 23 12:24AM

On 23/02/2015 01:36, Ramine wrote:
[snip]
 
> So from now on don't say that i didn't invented algorithm and libraries..
 
> Thank you,
> Amine Moulay Ramdane.
 
Do you have a C++ question? Stop spamming this newsgroup with your nonsense.
 
Sausages.
 
/Flibble
"Chris M. Thomasson" <no@spam.invalid>: Feb 23 10:09AM -0800


> https://sites.google.com/site/aminer68/semacondvar-semamonitor
 
> Where do you have such this concepts and this objects in Java or C++ or C#
> tell me ?
 
Eventcount's, semaphores and condition variables have
been around for a long time:
 
http://dl.acm.org/citation.cfm?id=359076
 
I created a decent way to implement an eventcount a while back:
 
https://groups.google.com/d/topic/comp.programming.threads/qoxirQbbs4A/discussion
 
Does this mean I invented them? The answer is:
 
NO!
 
:^)
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Feb 23 05:28PM

What happened to James Kanze? I want James Kanze. I miss arguing with
him when he is fractally wrong.
 
Sausages.
 
/Flibble.
"Öö Tiib" <ootiib@hot.ee>: Feb 23 09:46AM -0800

On Monday, 23 February 2015 19:28:32 UTC+2, Mr Flibble wrote:
> What happened to James Kanze? I want James Kanze. I miss arguing with
> him when he is fractally wrong.
 
He is actively answering/commenting at stack overflow.
Nobody <nobody@nowhere.invalid>: Feb 23 01:22AM

On Sun, 22 Feb 2015 14:15:13 +0000, JiiPee wrote:
 
> So what encoding you guys use? UTF-8 or UTF-16? What is the
> recommendation and your experiences.
 
Use UTF-8 for anything written to a file or sent over a byte-oriented
communication channel (e.g. most network protocols).
 
Internally, use whatever works best for what you're going to do with the
data.
 
E.g. on Windows, you typically need to use wchar_t* (ignore the question
of whether it's UTF-16 or UCS-2; it isn't either of those, its JUST an
array of wchar_t). Windows filenames are arrays of wchar_t; if you use the
char* APIs (e.g. CreateFileA() or fopen()), the program will only be able
to access files whose name is representable in the active "codepage"
(essentially Microsoft-speak for "encoding").
 
> If not, how do you deal with these and what needs to be done so they can
> be used. Say I use Russian letters, how I practically find a certain
> letter and use all the SDT functions/classes.
 
If you need to do almost anything which "interprets" text, you need a
library such as ICU (site.icu-project.org).
 
The built-in methods of a std::string work with bytes, not "characters"
(in any sense of the word). Similarly, the built in methods of a
std::wstring work with wchar_t-s, not characters (the fact that a wchar_t
is closer to being equivalent to a character just makes the bugs less
obvious than if you'd used char instead).
 
A 16-bit wchar_t either means that it takes 1 or 2 values to represent a
single Unicode codepoint (UTF-16) or limits you to the basic multilingual
plane (UCS-2).
 
A 32-bit wchar_t gives you the full Unicode range with a 1:1
correspondence between values and codepoints, at the expense of using more
memory (potentially four times what you need if you mostly deal with
Latin-based languages).
 
But even that isn't really a "character" because of the existence of
combining characters, e.g. a lower-case letter a with an acute accent
could be represented as either the precomposed character U+00E1 = LATIN
SMALL LETTER A WITH ACUTE, or the sequence U+0061 = LATIN SMALL LETTER A
followed by U+0301 = COMBINING ACUTE ACCENT.
 
For comparisons, these forms ought to be equivalent, meaning that
strings need to be normalised (and there are 4 standard normal forms).
But software which deals with wide strings often treats them simply as
arrays of codepoints. This includes core Windows APIs, which will happily
allow you to create two files in the same directory with the same
(apparent) name but which differ in whether accented characters are
pre-composed.
 
Note that there is no normal form which guarantees that each "character"
is pre-composed, as not all characters have pre-composed forms (e.g.
Hangul (Korean) only has pre-composed forms for "modern" Korean, which
is insufficient for a number of uses).
 
You also have to deal with issues such as capitalisation being more
complex in languages other than English. E.g. the upper-case equivalent of
a German "sharp s" (looks a bit like lower-case "beta") is "SS" (two
characters). Turkish has dotted and un-dotted "I" characters, each with
lower-case and upper-case versions; lower-case dotted-I (i) and upper-case
un-dotted-I (I) are the same characters as Latin, but case conversion
using the rules for Latin will give the wrong result. Ligatures often have
lower-case, upper-case and title-case variants (i.e. to convert a string
to title case, the first character of each word must be converted to
title case, not upper case).
Juha Nieminen <nospam@thanks.invalid>: Feb 23 05:56AM

> 4) fits into std::string (std::wstring is unspecified if it is UTF-16 or
> UTF-32 or something else entirely)
> 5) is encoding of majority of internet text content
 
That's quite a unilateral view, as you didn't contrast it with the
advantages of UTF-16:
 
1) UTF-16 is faster to handle, especially if you can limit it to UCS-2
(but even if you don't.)
 
2) UTF-16 takes less space with many non-western languages, such as
Japanese. (Most, if not all, Japanese characters take 3 bytes with
UTF-8 but only 2 bytes with UTF-16.)
 
--- news://freenews.netfront.net/ - complaints: news@netfront.net ---
JiiPee <no@notvalid.com>: Feb 23 07:38AM

On 23/02/2015 01:22, Nobody wrote:
> wrong result. Ligatures often have lower-case, upper-case and
> title-case variants (i.e. to convert a string to title case, the first
> character of each word must be converted to title case, not upper case).
 
so does ICU -library handle these correctly, the uppercases? And others?
Paavo Helde <myfirstname@osa.pri.ee>: Feb 23 02:47AM -0600


> so does ICU -library handle these correctly, the uppercases? And
> others?
 
It very much depends on what is considered "correct". And this very much
depends on the intended purpose and scope of the program. Filenames, for
example, should be left intact by most of the code - if the user wants to
put mixed uppercase, conjugate pairs or zero-width space in filenames, then
that's what s?he ought to get. No ICU needed here.
 
On the other hand, when you are implementing a google-like text search an
arguably correct way is to find all possible cases/variants of the word
(e.g. "ferry" and "ferries", "color" and "colour", etc) in all of the
languages of the world (English being one of the simplest in this respect),
or at least in languages whose alphabets have been included in the Unicode
standard. ICU most probably does not cover this (but may help to some
extent).
 
hth
Paavo
"Öö Tiib" <ootiib@hot.ee>: Feb 23 09:18AM -0800

On Monday, 23 February 2015 07:56:34 UTC+2, Juha Nieminen wrote:
> > 5) is encoding of majority of internet text content
 
> That's quite a unilateral view, as you didn't contrast it with the
> advantages of UTF-16:
 
I mentioned that UTF-16 can be more convenient depending on platform
/ framework.
 
 
> 2) UTF-16 takes less space with many non-western languages, such as
> Japanese. (Most, if not all, Japanese characters take 3 bytes with
> UTF-8 but only 2 bytes with UTF-16.)
 
These are really only performance factors. Megabyte of Japanese takes
days to read for a person regardless if it is UTF-8 or UTF-16. If it
is meant for a computer to read and I need extreme performance then
I don't see the reason why to choose Japanese (or text I/O in general).
Ramine <ramine@1.1>: Feb 22 09:05PM -0800

Hello,
 
 
That was my last post here in this forum.
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Feb 22 08:58PM -0800

I correct: i didn't know than we say criterion for single,
and criteria for many criterions.. because i don't speak english enough
, so please read again i have corrected my post...
 
Hello...
 
 
 
Now more about "wisdom" and about what's an invention...
 
We have to have "wisdom" also to define more correctly what's an
invention...
 
So please follow with me because i will try to define more what's an
invention...
 
If we look at programming, how then can we define an invention in
programming ? we can take the sadistic way of thinking and define
it to have overall a quality of 9/10 and 10/10, but this is not
a correct way of defining what's an invention, so how can we define an
invention in programming and what's the correct way to define invention
? invention can be defined from the point of view of one "criterion", or
from the point of view of many "criterion", so what are those criteria
that we must think about when defining an invention, we have the
criterion of how easy to use is the library or program, and this is
like "art", it's like if you are painting a more "beautiful" picture, so
i will give you an example to understand me more, if you look for
example at my parallel varfiler here:
 
https://sites.google.com/site/aminer68/parallel-varfiler
 
you will notice that my parallel varfiler is a parallel hashtable
that can work from the memory and that can be saved manually to a
hardisk's file and that can be saved automaticly to a hardisk's file at
realtime: i mean everytime you add a key and its corresponding data, it
will add it immediatly to the memory and to the hardisk's file, so from
the point of view of the "easy" of use, we can consider it an invention
because the interface is easy to use and more beautiful to use, it's
like "art", you have to look at it like looking at a beautiful painting
picture... also the fact that it's a parallel hashtable that uses lock
striping and the fact that it supports those characteristics that i have
just talked about makes it a good condidate to be called an
invention...so if you understand me more, i am defining an invention in
programming also like a painting art, and i am telling you that if the
interface is creative in the easy of use, so if it's more beautiful than
other libraries, so we can call that an invention, my definition applies
to my other projects... and of course we can judge and define an
invention from the point of you of other criteria like efficiency and/or
speed and/or portability etc.
 
 
 
Thank you for your time.
 
 
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Feb 22 08:00PM -0800

Hello....
 
 
Now more about "wisdom" and about what's an invention...
 
We have to have "wisdom" also to define more correctly what's an
invention...
 
So please follow with me because i will try to define more what's an
invention...
 
If we look at programming, how then can we define an invention in
programming ? we can take the sadistic way of thinking and define
it to have overall a quality of 9/10 and 10/10, but this is not
a correct way of defining what's an invention, so how can we define an
invention in programming and what's the correct way to define invention
? invention can be defined from the point of view of one "criteria", or
from the point of view of many "criterias", so what are those criteria
that we must think about when defining an invention, we have the
criteria of how easy to use is the library or program, and this is like
"art", it's like if you are painting a more "beautiful" picture, so i
will give you an example to understand me more, if you look for example
at my parallel varfiler here:
 
https://sites.google.com/site/aminer68/parallel-varfiler
 
you will notice that my parallel varfiler is a parallel hashtable
that can work from the memory or that can be saved manually to a
hardisk's file or that can be saved automaticly to a hardisk's file at
realtime: i mean everytime you add a key and its corresponding data, it
will add it immediatly to the memory and to the hardisk's file, so from
the point of view of the "easy" of use, we can considere it an
invention because the interface is easy to use and mroe beautiful to
use, it's like "art", you have to look at it like looking at a beautiful
painting picture... also the fact that it's a parallel hashtable that
uses lock striping and the fact that it supports those characteristics
that i have just talked about makes it a good condidate to be called an
invention...so if you understand me more, i am defining an invention in
programming also like a painting art, and i am telling you that if the
interface is creative in the easy of use, so if it's more beautiful than
other libraries so we can call that an invention, my definition applies
to my other projects... and of course we an judge and define an
invention from the point of you of other criterias like efficiency
and/or speed and/or portability etc.
 
 
 
Thank you for your time.
 
 
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Feb 22 06:39PM -0800

Jerry Stuckle wrote to me:
 
>You didn't invent crap. All you did was implement already developed
>algorithms. Something any programmer does every day.
>All you're doing is making yourself look even more stupid.
 
 
You are a kind of stupid guy too..
 
Because you have to define what's an invention...
 
You are defining an invention as one that must have a quality of 9/10 or
10/10 and you are taking into account the criteria of "difficulty" an
the "size" of the invention, you are saying that an invention that is
not of a big size or/and of a degree of difficulty that is high is not
an invention, but your way of defining invention is a sadistic way of
defining what's an invention.
 
 
My inventions that i have talked before are inventions too, but
you have to have more "wisdom" to agree with me, you are a low
level person when it comes to the criteria of "wisdom".
 
 
 
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.lang.c+++unsubscribe@googlegroups.com.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)