i've got an assigment that requires me to overload some operators and add some objects together.
I will show the code and explain as good as I can.
void SArray::operator+= (const SArray &obj) { Sphere * tmp_arr; tmp_arr = new Sphere[obj.antalobjekt+this->antalobjekt]; //antalobjekt = //Gets amount of elements in the arrays.
[Code]......
m_arr is the inner array for storing elements, do ask if something is not clear enough. The copy constructor works, so i have not included it.
I'm developing C++ application in visual studio 2012. I have couple of C++ projects in my solution. I have put some library paths in every project's properties ( i.e ,Config properties - > C/C++ - > Additional Include Directories and Linker - > Additional Include directories ).I developed in debug mode, if i change to release mode, all library settings gone.Is there any possibility to retain all settings when change to debug to release mode and vice versa ?
I'm currently just trying C++ with SFML. So I've installe SFML 2.0 for Visual C++ 2010 Express 64 bit, and I get an error while trying to run the debug of my code.
I'm not sure what I'm missing. It is supposed to input and display player's name and score, calculate the average score, and display the players who scored below average.
It simply doesn't work. All I get is a black screen. Debug spits out an exit code of 1073741510 (0xc000013a).
Code: #include <iostream> #include <string> #include <iomanip> using namespace std;
const int arSize = 100; int inputPlayerData (string playerName [], int playerScore [], int &numPlayers);
You place a breakpoint at one of locations within the message loop. But I want the breakpoint to trigger when I click on the application window, for example. But I can't, it went so fast so long as I switch from VS to the application program, the breakpoint is hitted again, then the application is frozen again. I don't know how to setup a conditional breakpoint.
i changed my code from release to debug mode. when i try to debug it shows a dialog box that '... does not contain debug information press ok to continue"..
I have a MFC Com Dll that has a CDialog. In the OnCreate event I create an ActiveX control. The dll is hosted inside an executable of mine. In this scenario everything works fine!
The dll is also called from an external executable and then a Debug Assertion in OCCSITE.cpp occurs when I create the ActiveX control. I suspect that in the executable there is no AfxOleInit. I spend some time with this problem and tried to CoInitialize, OleInitialize, AfxOleInitModule and even AfxOleInit in the dll. But all that does not change a thing. If I understand the mechanics then this is an intended behaviour and should be done in the host exe.
In my executable m_bNeedTerm is 0 and in the external one (where the ActiveX does not work) it is -1. In AfxOleInit this is explained as a special flag to prevent the dll from doing an unnecessary OleInitialize. But as I said even if I call OleInitialize myself I get the Debug Assertion and the ActiveX is not visible.
Is there anything I can do to make the ActiveX control work in the external application? Obviously I cannot Change anything in the application...
I dumped all symbols into C:WindowsSymbols folder, It takes more than 2 minutes to load an application which really surprises me. Why and when should I use those symbols?
On fairly rare occasions, when attempting to debug one of my MFC applications on VS 2010, a compilation error is encountered, and instead of bringing up the customary Windows or MFC file with a arrow pointing to the problem, a disassembly appears with an arrow pointing to one of the assembler instructions.
Since Windows assembly language is hardly my forte, I do not know how to interpret the error. Furthermore, the Output usually indicates one or more 'first chance exceptions' but little more, and the Stack output usually quite sparse and often refers cryptically to some ntdll.dll!7c92a82c().
after having my previous thread removed due the project I was working on being usable for malicious purposes I was directed to the project suggestions page; from there I decided to go ahead with an FTP client. I am now looking into how I will go about this and it is looking very simple (too simple maybe I am missing something? ). I was wondering if the standard FTP web requests in the standard library will work with programs such as FileZilla. As far as I can think everything should follow the same standard but I just wanted to make sure. I will be setting up an FTP server on my PC with FileZilla if so and getting to work tonight!
Also, off topic questions; is it generally considered bad practice to include a lot of logical code in a Form class? I generally try to make other classes contain all my logic code no matter how small (such as connecting to a socket, or writing to files) but I often see people's personal projects have nearly all of their code thrown into the same class as a Form.
So i made an STL compatible container.And to make this work I had to make my own iterator (derived from std::iterator).
What is the portable (if any) and "well behaved" thing to do in case of usage anomalies.such as iterating an iterator too far, or passing an invalid index to a operator[]
Looking at how VC++ does things in something like std::array or std::vector.
Code:
iterator_type& operator+=(difference_type offset) {// increment by integer #if _ITERATOR_DEBUG_LEVEL == 2 if (size < index + offset) {// report error
[Code] .....
lots of names starting with underscores, so it's implementation specific. Is there even a "well behaved" thing to do ? Or is any such work always going to be compiler specific?
I am looking for UUID 64 bit compatible library. I have used BOOST UUID generator, but faced compatibility issues with stlport4 and iostream libraries compiling together.
Any other such UUID generator working on similar concepts that of BOOST UUID library!
I am not a C programmer (or a programmer at all). I am just a hobbyist who writes random code (i.e.: ignorant).C is not my area, and I my experience with it is quite LIMITED!Today, I found out that if I need to get "square root" in C I will be in trouble if I depend solely on the compiler..Is it possible to make the compiler to generate smarter code for this (quite trivial code):
Code:
void intprime_c(unsigned long* fprimes, unsigned long count) { unsigned long divc = 3; unsigned long num = 2; unsigned long sqr; unsigned long pfound = 0; }
[code]...
By "without ugly hacks" I mean using already existing code that came with GCC. Because the others did not need ugly hacks to perform better (it is all about being fair).To compute the "square root" in x86 one just need 3 instructions:
fild fsqrt fistp
But the compiler is generating a call to a "fsqrt" function and wasting a lot of time by doing this. If not, then why is it taking so long? Is it something wrong in my code (at least the output was verified to be the correct)?
Time taken to get the first 2500000 primes (x86_64):
Assembly = 72.400s (human written, unoptimized, coder level: newbie (i.e.: ignorant)) pascal = 75.200s (written by the same person) C (fsqrt) = 83.600s (written by the same person) C (sqrt) = 85.900s (written by the same person)
If it matters, I compiled the C code with this command: gcc -O2 -fno-omit-frame-pointer -fPIC -c ./prime.
I am trying to release my C++ app to run on desktops that dont have VS installed and have created an install shield app to install on the desired computer. my issue is even after packaging it, it still requires certain DLL's...I read online that I had to copy 'msvcr120.dll' and a few others to syswow64 and sys32 folders but now when I try run my app it just crashes before starting.
I think it sucks that Microsoft no longer packages required DLL's like it used to in 2010.
I am getting some weird errors while building in release mode. It works fine in debug mode. Libraries and includes are linked in both debug and release version, but it's acting like it's not.