dev-cpp-users

Re: [Dev-C++] dynamic array

[Alan T. <ala...@3n...>]

I could not compile the code below.        Thanks, Alan

From: ste...@ge...
Subject: Re: [Dev-C++] dynamic array
Date: Wed, 10 Jan 2001 05:12:37 -0800

entry_var new int[size_of_entry];
if(!entry_var)
{
    cout << "Unable to allocate memory!";
    getch();
    exit(-1);
}

delete(entry_var);

Re: [Dev-C++] dynamic array

[Alan T. <ala...@3n...>]

Fabien,
                The code below would not compile.  It could not find =
"size_of_entry."  Am I simply missing an #include header file?

                                                                         =
                       Thanks, Alan

From: "Fabien VIVES" <fv...@fr...>
Subject: Re: [Dev-C++] dynamic array
Date: Wed, 10 Jan 2001 12:30:58 +0100

int (*buffer)[];

buffer=3D(int*)malloc(size_of_entry*sizeof(int));

free(buffer);

RE: [Dev-C++] dynamic array

[James G. <Jam...@Cl...>]

Try
 
int entry_var new int[size_of_entry];
 
You still have to specify what the type of entry_var is.

Regards, 

James. 

 

-----Original Message-----
From: Alan Thomas [mailto:ala...@3n...]
Sent: Thursday, January 11, 2001 2:56 AM
To: dev...@li...
Subject: Re: [Dev-C++] dynamic array


I could not compile the code below.        Thanks, Alan
 
From:  <mailto:ste...@ge...> ste...@ge...
Subject: Re: [Dev-C++] dynamic array
Date: Wed, 10 Jan 2001 05:12:37 -0800

entry_var new int[size_of_entry];
if(!entry_var)
{
    cout << "Unable to allocate memory!";
    getch();
    exit(-1);
}
 
delete(entry_var);

 



* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
This electronic message and any attachment is intended to be 
read by the named addressee(s) only. 
Any other recipient should be aware that its contents may be 
legally privileged and/or confidential and that its use, 
disclosure, copying or distribution may be unlawful. 
Unless you are a named addressee, please delete this message 

Whilst C. & J. Clark International Limited has taken steps 
to prevent the transmission of computer viruses with electronic mail, 
responsibility for screening incoming messages and the risk of such 
transmission and its consequences lies with the recipient. 

C. & J. Clark International Limited 
Registered in England and Wales 
Company No. 141015 
Registered Office: 40 High Street, Street, Somerset BA16 0YA 
Telephone: +44 (0) 1458 443131 
Fax: +44 (0) 1458 447547 

Re: [Dev-C++] dynamic array

[Dee Z. <zs...@br...>]

On Wed, 10 Jan 2001, Alan Thomas wrote:

> I could not compile the code below.        Thanks, Alan
> entry_var new int[size_of_entry]; 
> if(!entry_var)
> {
>     cout << "Unable to allocate memory!";
>     getch();
>     exit(-1);
> }
> 
> delete(entry_var);

There are several problems with your code, firstly the syntax of line
containing the new operator is wrong, correctly it would bee  
 int *entry_var = new int[size_of_entry]; 
Then again it is not advisable to use the getch() function, because it
laks the portability, some compilers like TC++ suport this one, but I
stronglly doubt that compilers from the Linux world like g++, the one 
used by DevCpp will accept it.
 Lastly, the code promotes a bad style,  imagine that you write a program
were you allocate memory in lots of places (lines in the source code) and
you defend each allocation with a check, like you did (and you
should), this would lead to a code filled with error ckecks and still
bugy. What will you do if an allocation fails in a low level function,
because exit() will do no cleanup. Returning an error code will not solve
your problem beacuse soon you will have to face the nightmare of
errorpropagation trough different levels. The solution would be exception
handling suported by all modern compilers, like the one used by DevCpp. 

Generaly it would be:

try
{
    //do anything 
}
catch(...) //or a more specific type
{
  cerr<<"Failed to (something)"<<endl; //this can be more specific  
}

 You can find more info in any C++ manual. 





 

Re: [Dev-C++] dynamic array, additional corection

[Dee Z. <zs...@br...>]

I've forgot to mention the last line is also eronous
 it shold be 
    delete []name_of_the_your_varible




Zsombor