Thread: problem in mystring class

I'm sure default arguments are handled at the callers side, thus making "*this" being dereferenced outside the method where there is no class object.

You can't use "*this" before you are INSIDE the function.

What you could do is to use overloading, like this:

Code:

	mystring& lower_case(mystring& str)
	{
		for (int i=0; i<str.size(); i++)
		{
			if (isupper(str[i]))
			{
				str[i] = tolower(str[i]);
			}
		}
		return str;
	}

	mystring& lower_case()  // No argument - use "this"
	{
                return lower_case(*this);
	}

Edit: as the mystring& lower_case(mystring &str) doesn't touch "this", you could make it static.
--
Mats

Originally Posted by Magos

I'm sure default arguments are handled at the callers side, thus making "*this" being dereferenced outside the method where there is no class object.

Spot on, and good explanation - I never explained why you can't use "this" as a default argument value.

--
Mats

I also see a big, fat warning that says exception handling is disabled in project settings... This is on by default, so you must have disabled it. Hopefully for a reason. Hopefully a good one.

Do not compile using command lines.
Compile within the IDE. There's a reason the IDE can automatically compile for you and it's convenient and it's not error-prone.
Simply press F7 (if you've select C++ 6 settings).

Your current code will break and fold in so many ways because you aren't compiling correctly.
Again, use the IDE.

I'm really allergic to compiling stuff via the command line. It shouldn't be necessary.
Sheesh. You don't even know how to use the compiler properly and yet you compile using command-line interface.

ctrl-space gives you completion of the stuff you are typing. ctrl-shift-space (I think) gives the current parameters for function calls [etc].

--
Mats

Originally Posted by manav

- i want MSVC to complete my symbol names, show completions etc. for all the files that are needed in my project.
what is the easiest way to do it?

It's typically called IntelliSense. MSVc's intellisense is a little poor, but doable. If you type a method, it will automatically show the parameters for those functions. If you need to force it to show it, mats listen the shortcuts. Typically, I just bind it to Alt+q, which is easier to use.
And you could also try Visual Assist X for Visual Studio. Very, very nice intellisense and other stuff plugin. Not free, but 30-days trial. And if you can reset the trial, all the better

- how do i compile my project using MSVC if i need to run a few custom tools over my source files and other files added to project.
also those tools produce some source files which need to be compiled. but they are generated by the tools.
how i set the MSVC to use these newly created files and compile them as well.

To this end, use the Custom Build Step in the project settings. Pre-build is executed before the compiler is called. Pre-link is called before the linker is called and post-build is called after the linker is finished.
If you need to compile extra source files, try to manually enter extra arguments to the compiler under the project settings.

Originally Posted by manav

those features work if i use MSVC for writing window specific code.
but i am writing code which does not use any windows api directly, i am using eg. Qt, boost and other portable
networking libraries. i also have their sources. now MSVC can find the definitions/declarations, can show completions, can do a lot of things.
how do i make it to do all those nice things for my Qt programs?

and also how do i make MSVC to do intellisense kinda stuff with Qt API?

It will automatically parse and detect any headers you've included. So it should work with Qt, as well as your own source. You can also try deleting the intellisense database (the *.ncb file) in the project directory to see if it helps. No extra configuration should be necessary.
You can also try Visual Assist X.

and if any body have done Qt they know that Qt source files need to run qmake do a little magic with the source files.
from command line its as simple as this:
qmake -project
qmake -makefile
nmake
how do i perform only these steps for my project build?

I have no idea what those command lines do or how they interact with your code, I can only guess. But Qt sounds like a pain. It shouldn't have to rely on command lines to build the darn thing. Just ship a little Dll or some other form of binary for the different platforms or provide instructions on how to create one such for each platform.

Qmake -project I suppose makes some changes to your project. That's fine. You can call that in the pre-build step.
Qmake -makefile makes a makefile for... qt only or your project? Does it create some library you need to link to?

Isn't it normally advised against inheriting from standard containers (due to the lack of virtual destructor) and wouldn't that also apply to std::string?

In this case, particularly since you apparently want to use the member function to provide the ability to convert other strings as well, wouldn't a much better approach be to provide a free function to_lower and to_upper for std::string (or download boost and use the ones that are already provided there)?

Oh and now that you mention it...
If the tolower/toupper functions are part of your class, they should perform the action on the object itself. When I call myobj.toupper(), I expect it to transform (or return a new object) with upper case.
If you want it to be able to mainpulate another object, making it static.

Originally Posted by manav

so just including the headers and specifying the include path in settings will work? i will try and post later.

about the qmake steps:
well they just make everything ready so just doing an nmake will make my programs.
how do i configure MSVC to just run nmake or use my makefile generated by qmake?

You could call nmake in the pre-build stage, but I don't trust that makefile. I would rather find a solution that involves compiling Qt into a library and linking with that instead of messing with command lines and make files. It's only going to be a headache in the end.