Strings copyingmore than expected

[taupune]

Hi ,I am doing some strings operation but it seems that compiler is doing extra copping.
Can someone else verify this or is it my sloppy coding?

Also I had to write
std::cin ...etc otherwise compiler would like the code without that expression in main function.
I am using Visual studio 2010.

#include <iostream>
using namespace std;
#include "string.h"

void disect (char TheMessage[], int startloc, char messagepart[], int messagelength);
void ResultCodeTable ( char Result[]);

int main ()
{

char test[3];
char message [140];
char enter;
std::cout << "hello enter the mesage: "<<endl;
std::cin>> message;
std:: cout<<"uncopied string: " <<test<<endl;
disect(message,3,test, 3);
std:: cout<<"copied string: " <<test<<endl;
std::cout<<"this is the message: "<<message<<endl;
std::cin>> enter;
return (0);
}


//Dissect cuts the mesage into several parts , where each part provides the separate meaning of itself

void disect (char TheMessage[], int startloc, char messagepart[], int messagelength)
{
cout<< "this is pre message part inside function printing: "<<messagepart<<endl;
cout<<"start loc is:"<<startloc<<" end loc is "<<messagelength<<endl;
for ( int i = 0; i<messagelength; i++)
{
messagepart= TheMessage[startloc];
startloc++;
cout<<"message part array : "<<messagepart<<endl;
cout<<"message original mesage : "<<TheMessage<<endl;
}
cout<< "end of function execution inside function printing: "<<messagepart<<endl;
}

 

[chiro]

Hi ,I am doing some strings operation but it seems that compiler is doing extra copping.
Can someone else verify this or is it my sloppy coding?

Also I had to write
std::cin ...etc otherwise compiler would like the code without that expression in main function.
I am using Visual studio 2010.

#include <iostream>
using namespace std;
#include "string.h"

void disect (char TheMessage[], int startloc, char messagepart[], int messagelength);
void ResultCodeTable ( char Result[]);

int main ()
{
	
	char test[3];
	char message [140];
	char enter;
	std::cout << "hello enter the mesage: "<<endl;
	std::cin>> message;
	std:: cout<<"uncopied string:   " <<test<<endl;
	disect(message,3,test, 3);
	std:: cout<<"copied string:   " <<test<<endl;
	std::cout<<"this is the message: "<<message<<endl;
	std::cin>> enter;
	return (0);
}


//Dissect cuts the mesage into several parts , where each part provides the separate meaning of itself

void disect (char TheMessage[], int startloc, char messagepart[], int messagelength)
{
	cout<< "this is pre message part inside function printing: "<<messagepart<<endl;
	cout<<"start loc is:"<<startloc<<"  end loc is "<<messagelength<<endl;
	for ( int i = 0;  i<messagelength; i++)
	{
		messagepart[i]= TheMessage[startloc];
		startloc++;	
		cout<<"message part array : "<<messagepart[i]<<endl;
		cout<<"message original mesage : "<<TheMessage[i]<<endl;		
	}
	cout<< "end of function execution inside function printing: "<<messagepart<<endl;
}

This is just a dummy post to put code tags around your code. As a pointer if you post code in the future but CODE and /CODE tages with square braces around them.

 

[phiby]

Hi ,I am doing some strings operation but it seems that compiler is doing extra copping.
Can someone else verify this or is it my sloppy coding?

It's your coding.

Made a small change to your disect function

void disect (char TheMessage[], int startloc, char messagepart[], int messagelen
gth)
{
    cout<< "this is pre message part inside function printing: "<<messagepart<<e
ndl;
    cout<<"start loc is:"<<startloc<<" end loc is "<<messagelength<<endl;

    int i;
    for ( i = 0; i<messagelength; i++)
    {
        messagepart[i]= TheMessage[startloc];
        startloc++;

        cout<<"message part array : "<<messagepart[i]<<endl;
        cout<<"message original mesage : "<<TheMessage[i]<<endl;
    }
    messagepart[i] = 0;

    cout<< "end of function execution inside function printing: "<<messagepart<<
endl;
}

A lot of standard library functions expect a 0 ('\0') to indicate end of string.


Also if you use C++ strings instead of C strings, the program becomes much easier

#include <iostream>
#include <string>

using std::cin;
using std::cout;
using std::string;

int main()
{
        string message;
        string test;

        cout<<"Enter message: ";
        cin>>message;


        test = message.substr(3,3);
        cout<<test<<'\n';

}

 

[chiro]

Ok I had a look at your code and I will share my thoughts.

The first thing is that it seems that are you passing the two arguments for your disect function by value and not by reference.

The difference between the two is that passing by value passes a copy of the actual data on the stack to the function whereas passing by reference gives the function a pointer to the object. In C, you use a pointer to the object to pass by reference and if you are using C++ you can use an ampersand '&' to pass the pointer to the function, but still treat the object like you are treating it in your function. If you are unaware of these things it would be helpful for your to look these up.

Also you have not initialized your character arrays and you are printing the test array that is not initialized at the beginning of your code. You also need to make sure the strings are terminated properly. I don't know if this was a mistake or not.

Another thing to help us would be to give us the output from the console window. Since you are using cout to dump output to the standard output device, this information will basically tell us exactly what is happening.

Also another tip would include to do things like make sure that you do not copy parts of the string that don't exist. This would mean checking that the part of the string you are copying in your disect function checks to make sure that all the characters that are being copied are in the range of characters that is inputted by the user. Usually in C++ people use either things like a standard library implementation for string or they write their own custom class that has an extra variable for the string size. In addition to this, they also add class functions to do all this kind of checking automatically so you don't have to.

 

[phiby]

Ok I had a look at your code and I will share my thoughts.

The first thing is that it seems that are you passing the two arguments for your disect function by value and not by reference.

The difference between the two is that passing by value passes a copy of the actual data on the stack to the function whereas passing by reference gives the function a pointer to the object. In C, you use a pointer to the object to pass by reference and if you are using C++ you can use an ampersand '&' to pass the pointer to the function, but still treat the object like you are treating it in your function. If you are unaware of these things it would be helpful for your to look these up.

His argument passing has no problems.

char message[140];

to function f, if you pass
f(message);

What you are actually passing is
f(&message[0]);

So you are passing a pointer to the first element of the array.
So a copy is created, but not a copy of the array, but a copy of the pointer, which is exactly what you want.

Also you have not initialized your character arrays and you are printing the test array that is not initialized at the beginning of your code.

message gets initialized by cin
test gets initialized in disect

You also need to make sure the strings are terminated properly. I don't know if this was a mistake or not.

message gets terminated by 0 ('\0') by cin.
test is not - that's the main mistake in his code.

 

[chiro]

His argument passing has no problems.

char message[140];

to function f, if you pass
f(message);

What you are actually passing is
f(&message[0]);

So you are passing a pointer to the first element of the array.
So a copy is created, but not a copy of the array, but a copy of the pointer, which is exactly what you want.

I think I've mixed up something here.

If you pass say something like char myString[140], then that gets put on the stack but if you pass it without a size then that gets passed by reference. It's been a while since I've done any serious coding so thanks for the correction.

 

[Mark44]

I think I've mixed up something here.

If you pass say something like char myString[140], then that gets put on the stack

No. What gets passed is the address of the string in memory, which is to say &myString[0], just as phiby said.

This is the way it works in C and C++ if you're working with strings as arrays of type char.

In general, the name of an array is an address, so an actual parameter that is the name of an array is passed by reference.

but if you pass it without a size then that gets passed by reference. It's been a while since I've done any serious coding so thanks for the correction.

 

[chiro]

No. What gets passed is the address of the string in memory, which is to say &myString[0], just as phiby said.

This is the way it works in C and C++ if you're working with strings as arrays of type char.

In general, the name of an array is an address, so an actual parameter that is the name of an array is passed by reference.

So just do I don't forget next time, how do you pass an array on the stack in C/C++ functions? As an example, a character array?

 

[phiby]

So just do I don't forget next time, how do you pass an array on the stack in C/C++ functions? As an example, a character array?

There is no simple way to pass a copy of the whole array in C (you could do it in a twisted way - by wrapping the array in a struct & passing the struct by value).

In C++, if you have a std::string, it can be passed by value semantics.