C / C++ / MFC

char * buff = (char*)malloc(atoi(argv[2]));

Endomlic wrote:

but it acts as if it's not assigning buff with a size. in other words it's not working.

char size[]="10";
char * chBuff = (char*)malloc(sizeof(char)*atoi(size));
strcpy(chBuff,"TestMail");
for(int i=0;i<8;i++)
{
	printf("%c",chBuff[i]);
}

VuNic wrote:

How will it allow you to create buffers without knowing the size?

Endomlic wrote:

I guess in gcc argv 0 is the program name.

pandit84 wrote:

i want to convert a key board input...

Gary R. Wheeler wrote:

like in C#? C++ doesn't have static constructors. I don't know if C+0x is going to support that or not (it might be nice if it did).

Gary R. Wheeler wrote:

With an instance constructor, you can set static members just like instance members. Each instance of a class can modify a static member.

class CodeProject
{
  static int x;
  int y;
   CodeProject()
  {
    x=0;
    y=0;
  }
};

int CodeProject::x;

Gary R. Wheeler wrote:

Stricly speaking, you don't have to initialize the value when you define it:

Gary R. Wheeler wrote:

n the CPP source file. The language designers left it up to the programmer where to place the definition, rather than arbitrarily placing it somewhere themselves. Interestingly enough, the C++ language places relatively few requirements on where in your source code you do things.

VuNic wrote:

why not they allow us to define it in the constructor?

Gary R. Wheeler wrote:

here isn't a way for the compiler to tell the difference between initialization, which you only want to do once for a static member, and a normal assignment, which you may want to do every time you construct a new instance.

Gary R. Wheeler wrote:

delete this;

VuNic wrote:

The above won't work without we initializing it again in the .cpp.

Stuart Dootson wrote:

You would need some intelligence in the linker to merge all allocations of the static item. Now, that intelligence might exist today, but it sure didn't back when Bjarne designed C++.