i was surfing around and stumbled across the bitset.. i'm curious - how does it work??? i didnt think it was possible 2 address single bits in memory..
i got some very funny results with this code:
here's wt i get:
4 0x0012FF74 0x0012FF6C 0x0012FF64
y is sizeof(a) 4????
if i make a bitset of 33 bits, then th size becomes 8, so i gues it gets stored in multiples of 4 bytes??? so if ur nt actualy storing single bits, then wt r bitsets used 4???
and wts with the the addresses?? how is it tht the adress of the same bit is different the second time??? (and even if i change the number in the 4th line from 4 to nethin else, i stil get the same output)
clearly, u cant refer 2 th address of a single bit... then how is a bitset impelemnted???
and because of al this, wudnt they be inherently slow to access???
I seem to be getting this error,actually the debugger juist stops and then gives me a dialog box saying Debug Assertion Failed(with ignore,retry,abort).However,none of them help my proj in running.
The box gives me something like
Debug Assertion Failed
File : f:\vs70builds\vc\MFCATL\ship\atlmfc\include\afxcoll.ini
line : 204.
This appears on a particular point everytime,when I try to execute the line
pVar = (CVarData*) m_arrayVariables.GetAt(iVarIndex);
(where CVarData* pVar; & CPtrArray m_arrayVariables;)
This is in a function called GetValue(a member of class CVars).The variable of CVars used to get here is initialised in the constructor of the original class(CHPMumsCtrl) and is a part of public members of the calling class(CCalc).
If anyone can tell me what to do here,then it will help a lot.Can someone tell me the cause anything at all will be helpful.
It is an C++ engine that acts as a parser,ie it recieves messages and sends messages. On recieving messages it parses them and then takes action accordingly. It firsts loads a script for processing(parsing),then it displays the script according to the parsed results and sends messages accordingly to the server.
Hi Mr. Arjun
at what point you are getting the debug assertion i.e. during receiving or parsing.
i think it is at the time of parsing,it ususal programmer break the boundry of MS collection arrays.
as assertion is not applicable in RELEASE MODE, thats why i ask you to Build in relase Mode (though it bad programming habit to test the product in release mode),but it surely tell you where you getting error.
The debug assertion failure that i get is a run time error...but in the release mode i get so many errors(build/compile),i cannot even get the project to run,can u help me clear these errors then please
aj1682 wrote: Can anyone tell me what this method GetAt actually does?,What it returns,where it Getsfrom etc.
You are talking about the function CPtrArray::GetAt(), right? Then reading the relevant MSDN entry will help you more than anyone of us possibly could.
"We trained hard, but it seemed that every time we were beginning to form up into teams we would be reorganised. I was to learn later in life that we tend to meet any new situation by reorganising: and a wonderful method it can be for creating the illusion of progress, while producing confusion, inefficiency and demoralisation."
Once upon a time i created a wrapper for the Drives Enumertaion and for other information, but due to my poor english i am unable to document it enough.I will try to redocument whole article some day.......
may be you be able to use that Wrapper Class Easily,it can be found here[^]