|
No one help me?  
|
|
|
|
|
I need to read 512 bytes from a file and convert into a string. But first few bytes (10-15) are 0x0 and when I pass this buffer to string, I am getting empty string.
Buffer is having correct 512 bytes.
CStringA szMailContent(buffer);
Please help.
|
|
|
|
|
john5632 wrote: first few bytes (10-15) are 0x0
john5632 wrote: Buffer is having correct 512 bytes.
Both of these statements cannot be true. Either the buffer contains 512 characters or it contains something else, which may include some characters. Try showing how you read the buffer and what it contains when the read completes.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
john5632 wrote: But first few bytes (10-15) are 0x0
I think that is the key to your problem. The string of characters that will be placed into the szMailContent instance will consist of all characters in your buffer up until the first 0x0 is encountered. If you need your instance to be able to contain 0x0 characters, you will need to use some other class for that. 
Chris Meech
I am Canadian. [heard in a local bar]
In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
|
|
|
|
|
Something like:
BYTE buffer[512];
CFile file;
file.Read(buffer, sizeof(buffer));
"One man's wage rise is another man's price increase." - Harold Wilson
"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
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
You can make sure like this:
CFile file;
Char tempBuf[512];
file.Read(tempBuffer, 512);
|
|
|
|
|
manem21k wrote:
You can make sure like this:
CFile
file;
Char tempBuf[512];
file.Read(tempBuffer, 512);
Actually this will not work.
Char tempBuf[512]; <== wont compile there'e no Char data type
char tempBuf[512]; <== will compile
file.Read(tempBuffer, 512); <== wont compile, tempBuffer isn't declared
file.Read(tempBuf, 512); <== will compile
In other words see David's reply.
|
|
|
|
|
Thanks for correcting the typos. Yeah I have't run this program but just sure the code will resolve the problem.
|
|
|
|
|
Why do you want to initialize a CString with binary data?
Veni, vidi, vici.
|
|
|
|
|
Hi
I want to use this control.
I have VS2008. I create CMyDialog and create CGridCtrl m_Grid as a member. Then I fill grid without problem. I need to take focus cell text when I list grid by arrow down arrow up keys. What I have to do in message map of my class CMyDialog to react on these actions. Can You help me? Where I shoud look in documentation?
|
|
|
|
|
I already answered this question here[^]. Please post in one forum only.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Specifically this statement:
printf("Chi square distribution for %s samples is %1.2f (%1.4f), and randomly\n",
String_Value, chisq, chisq);
I re-implemented this program in MASM to speed it up and I get the following difference (note that I added the (%1.4f)) to display the pre-rounded number to see why I was getting differences:
------------------------------------------------------------------ 17
Chi square distribution for 2048 samples is 6.13 (6.1250), and randomly
-------------------------------------------------------------- 17
Chi square distribution for 2048 samples is 6.12 (6.1250), and randomly
The question is, which one is correct according to the C spec? Should 6.1250 round up to 6.13 or should it take 6.1250+ to round up?
There are other questions such as the following:
printf("of this %s %s file by %d (%2.2f) percent.\n\n", String_Value, samp,
(short) (((100 * ((binary ? 1 : 8) - ent) / (binary ? 1.0 : 8.0)) + 0.5)),
((100 * ((binary ? 1 : 8) - ent) / (binary ? 1.0 : 8.0))));
The cast to a (short) seems to truncate a 5.7 to 5, I had to add the (.... + 0.5) just before the cast in order to get the rounded number. Again, I added the (%2.2f) to display the rounding differences.
Which is correct according to the C spec, rounding or truncation?
The program being re implemented is John Walker's ENT.
Dave.
|
|
|
|
|
I think the rules for rounding when a floating point's decimal part ends in 5 is, round up if the previous digit is even, and down if it's odd. So 6.125 rounds up to 6.13 but 6.115 would round down to 6.11; this is easy to check. In the second instance if you cast a float to an integer it discards the decimal part.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Richard,
Very interesting. I pulled up my 8087 book "THE 8087 PRIMER", John F. Palmer and Steven P. Morse and looked up rounding. The nearest to what you described is the "round to nearest Even" mode, not the round to the nearest Odd as you described. Are you sure about this? Is it in some C spec?
If you are programming the FPU and want to cast a float to an integer, you just execute an FIST or FISTP, which will round to the specified rounding mode which is usually "round to nearest Even" unless you specifically set the mode to "round to 0" before you store the value.
Dave.
|
|
|
|
|
Well I did not have a reference to hand so it's just from what I recall during other development. However, you seem to have more up to date information than me.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Richard,
I'm not trying to argue, just trying to find out what the spec says.
"THE 8087 PRIMER" is just a spec, from the Senior Staff Engineers at Intel Corp. explaining why they did what they did. How C uses the hardware should be specified somewhere.
Dave.
|
|
|
|
|
Member 4194593 wrote: I'm not trying to argue
I did not mean to imply that you were; I am more than happy to have my assumptions corrected. As to what the C/C++ compiler should do in these cases, you could look at http://www.stroustrup.com/[^], or the Microsoft reference pages[^].
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Richard,
Thank you for the links. I'll report back with anything I find (if I can understand it).
Dave.
|
|
|
|
|
Richard,
I did find out that a float cast as a (short) is truncated, but not yet found out about rounding in printf.
Dave.
|
|
|
|
|
Richard,
I did find out only that the number will be rounded to the number of specified precision digits, but there is no mention of which rounding method is used! I did send feedback that I was dissatisfied with their answer.
Dave.
|
|
|
|
|
|
jschell,
Thank you for the excellent link, at least it references a spec, namely IEEE.
Personally, I do not think it really makes any difference what the least significant digit is rounded to, but when you are converting a program and want to insure that the conversion is accurate, and the program has many options, the easiest approach is a batch file calling the two programs, supplying the different input files and options to be processed, and then using a file compare routine to compare the outputs for each test instance.
In the case of ENT compiled under Visual Studio 2008, I can see truncation, rounding to an even, and common rounding, all in one program. Makes it a bit difficult to "emulate" the original program.
I have examined all of the test output (the diffs) for all of the test instances, and all of my results match the ENT results except possibly for that last digit. At this point I am calling this a valid conversion, and a huge learning experience. At least my version is about 5 times as fast for huge files as ENT (16 GB - all DWORD values for a full 2^32 period) 6 min vs 28 min.
Dave.
|
|
|
|
|
I'm not sure if i should put this question in this forum or the Graphics forum, as the description in graphics forum only says DirectX,OpenGL or GDI.
So I was trying this graphics.h library that can crate simple graphic for console app. Everything works just fine until I multithreaded? it.
Ok, here is the code:
#include<graphics.h>
void drawrect(int l,int t,int r,int d,int col){
if(col==0)setcolor(RED);
else setcolor(BLUE);
rectangle(l,t,r,d);
}
void drawpiece(int l,int t,int r,int d,int col){
for(int i=1;i<5;i++)
drawrect(i*16+l,t,i*16+r,d,col);
}
DWORD WINAPI Thread2(void* lparam){
int px2=161,py2=17;
for(int i=0;i<10;i++,py2+=16,delay(100))
drawpiece(px2,py2,px2+16,py2+14,1);
}
int main()
{
initwindow(600,600,"TEST");
CreateThread(0,0,&Thread2,NULL,0,0);
int px1=17,py1=17;
for(int i=0;i<10;i++,py1+=16,delay(100))
drawpiece(px1,py1,px1+14,py1+14,0);
getch();
return EXIT_SUCCESS;
}
What i'm trying to do is to make two set of blockline. where first set is red and second set is blue.
this code makes the color mixed up.
So that's it. Any help would be greatly appreciated.
|
|
|
|
|
I have not checked your arithmetic, but it may be that the start points and limits of your rectangles are not correct.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
I have checked the arithmetic and it works just fine if i don't multithread it.
This works just fine:
#include<graphics.h>
void drawrect(int l,int t,int r,int d,int col){
if(col==0)setcolor(RED);
else setcolor(BLUE);
rectangle(l,t,r,d);
}
void drawpiece(int l,int t,int r,int d,int col){
for(int i=1;i<5;i++)
drawrect(i*16+l,t,i*16+r,d,col);
}
int main()
{
initwindow(600,600,"TEST");
int px1=17,py1=17;
for(int i=0;i<10;i++,py1+=16,delay(100))
drawpiece(px1,py1,px1+14,py1+14,0);
int px2=161,py2=17;
for(int i=0;i<10;i++,py2+=16,delay(100))
drawpiece(px2,py2,px2+16,py2+14,1);
getch();
return EXIT_SUCCESS;
}
I'm really starting to think that this might be a problem from graphics.h
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
