C/C++ arrays are zero based.
While there's nothing wrong in liking better one-based arrays, it is wiser remaining stuck with zero-based ones, because:
You need extra work to make your arrays alive (extra work is generally bad)
Most people use the opposite convention: that means you have to adapt your data to any time you've to deal with other people code, like libraries, etc..
Neverthless, there are few examples of consistently used one-based arrays, for instance, all "Numerical Recipes" book source code uses it (the authors simply ignore array item 0).
Like all 'alien' conventions it's a bit difficult to grasp immediately, but after some experience with, becomes 'natural'.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
thanks, well i was trying to make the app more easy to follow, because 0 based arrays are not so intuitive, we starts count in one, i think that the easy way is make the array one element bigger but when you have many arrays is a waste of memo, so i would try with your seggest.
I'm using g++ version 4.4.1 in Ubuntu and I am trying to use the SSE3 intrinsic for the HADDPS instruction. I have included the header file:
and I have in my code:
num3 = _mm_hadd_ps(num3, num3);
where num3 is of type __m128.
Unfortunately, when I go to compile, I get the error message:
error: ‘_mm_hadd_ps’ was not declared in this scope
Other SSE intrinsics, such as _mm_setzero_p or _mm_mul_ps, work fine. Those are SSE or SSE2 intrinsics though...
Does anyone know if g++ supports the _mm_hadd_ps intrinsic? Or maybe there is another intrinsic for this instruction? Any help is much appreciated.
In my CSocket client program, when I repeatedly relogon from one client, I see "Socket Notification Sink" exception.
I read some posts on the forum about this error, which said: dummy window and something else - anyway, it is bad design of CSocket.
In my case, I guess the exception is around function CSocket::Close(), CSockt::Connect() and CSocket::Send() for sending first message. I also guess the exception is caused by if CSocket is not ready for use.
I used try-catch, but the exception can not be catched.
Have you noticed that he's just posted the same thing below? He's given it one hours time, and after not responding to any queries that David asked, he deleted his previous query and started a new thread (same title, same contents, no more information).
Are you implying that the problem could not be in your code?
Do you have any comments to avoid the exception?
Yes. Fix the code that is causing the exception. Now before you get your undies all in a bunch and whine that my suggestion is not helpful and ban me from commenting further, think about the question you've asked and if you really think you've provided enough information for us to be helpful.
BTW: do raw socekt functions have the problem?
Have you tried using them to narrow the problem down?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons