Hi All,
I have a question which might sound very basic.
I have a simple structure:
struct simple{
void *buffer;
};
typedef struct simple Simple;
In my function I do this:
void do_Something(){
Simple *simp_struct;
simp_struct->buffer = malloc(10 * sizeof(int *));
call_func((void **)((int **)(simp_struct->buffer)));
....
}
The function call_func has this prototype:
call_func(void **buf);
I am confused with this piece of code:
call_func((void **)((int **)(simp_struct->buffer)));
What does this construct mean? How is that simp_struct->buffer
(which is a void *) is being cast to a int** followed by a
cast to void ** and passed to call_func ?
Rgds.
Mirage 31 3867
Twister wrote: Hi All,
I have a question which might sound very basic.
I have a simple structure:
struct simple{ void *buffer; }; typedef struct simple Simple;
In my function I do this:
void do_Something(){
Simple *simp_struct; simp_struct->buffer = malloc(10 * sizeof(int *));
call_func((void **)((int **)(simp_struct->buffer))); .... }
The function call_func has this prototype: call_func(void **buf);
I am confused with this piece of code: call_func((void **)((int **)(simp_struct->buffer)));
What does this construct mean? How is that simp_struct->buffer (which is a void *) is being cast to a int** followed by a cast to void ** and passed to call_func ?
Rgds. Mirage
I mistyped part of my previous mail:
This piece of code: I am confused with this piece of code: call_func((void **)((int **)(simp_struct->buffer)));
should be this:
for(i=0; i<10 ;i++)
call_func((void **)((int **)simp_struct->buffer + i));
My question remains the same. What does the above
construct mean?
Rgds.
Mirage
Twister said:
<snip> simp_struct->buffer = malloc(10 * sizeof(int *));
call_func((void **)((int **)(simp_struct->buffer)));
Why not just do this:
call_func(&simp _struct->buffer);
Casts are almost always wrong.
The function call_func has this prototype: call_func(void **buf);
I am confused with this piece of code: call_func((void **)((int **)(simp_struct->buffer)));
What does this construct mean?
It means you don't (or whoever wrote it doesn't) understand what casting is
for.
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)
In article <k8************ *@news.oracle.c om>,
Twister <tw*****@nospam .com> wrote: struct simple{ void *buffer; }; typedef struct simple Simple;
void do_Something(){
Simple *simp_struct;
simp_struct is an uninitialized pointer after that statement.
simp_struct->buffer = malloc(10 * sizeof(int *));
But there you are using it as if it was initialized.
simp_struct->buffer involves dereferencing simp_struct first and
then accessing the structure component named buffer there, so
simp_struct needs to be given a value first.
call_func((void **)((int **)(simp_struct->buffer))); .... }
--
Prototypes are supertypes of their clones. -- maplesoft
Walter Roberson said: In article <k8************ *@news.oracle.c om>, Twister <tw*****@nospam .com> wrote:
struct simple{ void *buffer; }; typedef struct simple Simple;
void do_Something(){
Simple *simp_struct;
simp_struct is an uninitialized pointer after that statement.
Good spot. I didn't see that. Silly me.
Everything I said still applies, but that applies too!
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)
Twister said: for(i=0; i<10 ;i++) call_func((void **)((int **)simp_struct->buffer + i));
My question remains the same. What does the above construct mean?
That's a major difference.
What you have now is a bug.
simp_struct->buffer has type void *, so you can't do pointer arithmetic on
it. So the cast to int ** gives you a value (of type int **) with which you
/can/ do pointer arithmetic. That is, (int **)simp_struct->buffer + i gives
you the address of the i'th int **, starting at simp_struct->buffer. The
expression has type int **. The cast to void ** is an error because there
is no guarantee that an int ** can be copied to a void ** without loss of
information.
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)
Richard Heathfield wrote: Twister said:
for(i=0; i<10 ;i++) call_func((void **)((int **)simp_struct->buffer + i));
My question remains the same. What does the above construct mean?
That's a major difference.
What you have now is a bug.
simp_struct->buffer has type void *, so you can't do pointer arithmetic on it. So the cast to int ** gives you a value (of type int **) with which you /can/ do pointer arithmetic. That is, (int **)simp_struct->buffer + i gives you the address of the i'th int **, starting at simp_struct->buffer. The expression has type int **. The cast to void ** is an error because there is no guarantee that an int ** can be copied to a void ** without loss of information.
simp_struct->buffer was earlier initialized to point to memory
of 10 (int *)'s. So isn't just saying, (int *)simp_struct->buffer + i
correct? Why cast it to an (int **), unless i'm not passing it
to a function which expects a int ** or a void ** ? Please correct
me if i'm wrong here.
Rgds.
Mirage
Twister said: Richard Heathfield wrote: Twister said:
for(i=0; i<10 ;i++) call_func((void **)((int **)simp_struct->buffer + i));
My question remains the same. What does the above construct mean?
That's a major difference.
What you have now is a bug.
simp_struct->buffer has type void *, so you can't do pointer arithmetic on it. So the cast to int ** gives you a value (of type int **) with which you /can/ do pointer arithmetic. That is, (int **)simp_struct->buffer + i gives you the address of the i'th int **, starting at simp_struct->buffer. The expression has type int **. The cast to void ** is an error because there is no guarantee that an int ** can be copied to a void ** without loss of information.
simp_struct->buffer was earlier initialized to point to memory of 10 (int *)'s. So isn't just saying, (int *)simp_struct->buffer + i correct?
No, that would point to the i'th int, not the i'th int *.
Why cast it to an (int **),
To get a pointer to the i'th int *.
Please correct me if i'm wrong here.
The cast to int ** is correct, but doesn't help you solve your void **
problem.
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)
Richard Heathfield wrote: Twister said:
Richard Heathfield wrote:
Twister said: for(i=0; i<10 ;i++) call_func((void **)((int **)simp_struct->buffer + i));
My question remains the same. What does the above construct mean?
That's a major difference.
What you have now is a bug.
simp_struc t->buffer has type void *, so you can't do pointer arithmetic on it. So the cast to int ** gives you a value (of type int **) with which you /can/ do pointer arithmetic. That is, (int **)simp_stru ct->buffer + i gives you the address of the i'th int **, starting at simp_struct->buffer. The expression has type int **. The cast to void ** is an error because there is no guarantee that an int ** can be copied to a void ** without loss of information.
simp_struct->buffer was earlier initialized to point to memory of 10 (int *)'s. So isn't just saying, (int *)simp_struct->buffer + i correct?
No, that would point to the i'th int, not the i'th int *.
Why cast it to an (int **),
To get a pointer to the i'th int *.
Please correct me if i'm wrong here.
The cast to int ** is correct, but doesn't help you solve your void ** problem.
Thanks. That clarified part of my question.
The cast to void ** is an error because there is no guarantee that an int ** can be copied to a void ** without loss of information.
The malloc just allocated enough space for 10 (int *) pointers.
The pointers themselves are not pointing to valid memory. So If I cast
simp_struct->buffer finally to a void **(after the cast to an int **)
and pass it to a function which allocates some momory and points these
int *'s to valid memory, am I not doing the right thing ? Where is the
loss of information happening ?
Rgds.
Mirage
Twister said: Richard Heathfield wrote:
>The cast to void ** is an error because there is no guarantee that an >int ** can be copied to a void ** without loss of information. The malloc just allocated enough space for 10 (int *) pointers.
Yes.
The pointers themselves are not pointing to valid memory.
Right.
So If I cast simp_struct->buffer finally to a void **(after the cast to an int **) and pass it to a function which allocates some momory and points these int *'s to valid memory, am I not doing the right thing ?
No, I'm afraid not.
Where is the loss of information happening ?
There's no guarantee that information is lost. There's just no guarantee
that it's not lost! Either could happen. In other words, it might "work"
just fine on your development machine - and then break on some other box.
The problem is that, whilst the Standard guarantees that you can use void *
to store any object pointer (without loss of information), it doesn't offer
the same guarantee for void **.
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously) This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Jacob Jensen |
last post by:
This question has probably been asked a million time, but here it comes
again. I want to learn the difference between the three type cast operators:
static_cast, reinterpret_cast, dynamic_cast. A good way to do this is by
example. So I will give an example and please tell me what you think:
I have a base
class A
with a virtual destructor, and a
class B
that is it inherits publicly from A and defines som extra stuff.
|
by: He Shiming |
last post by:
Hi,
I'm having a little bit of trouble regarding pointer casting in my program.
I don't understand why the following two cases produce different results.
Case 1:
IInterface *pInterface = new CImplementation();
pInterface->Method();
Case 2:
|
by: rihad |
last post by:
Hi, I've this question: suppose we have two differently typed pointers:
struct foo *foo;
char **array;
Becase one can always legally cast any pointer to (void *), and becase (void *)
is assignable to any pointer type, is it ever necessary to cast when assigning
one pointer type to another? I.e. since
foo = (void *) array;
|
by: Brian Blais |
last post by:
Hello,
I saw on a couple of recent posts people saying that casting the return
value of malloc is bad, like:
d=(double *) malloc(50*sizeof(double));
why is this bad? I had always thought (perhaps mistakenly) that the
purpose of a void pointer was to cast into a legitimate date type. Is
this wrong? Why, and what is considered to be correct form?
|
by: ytrama |
last post by:
Hi,
I have read in one of old posting that don't cast of pointer which
is returned by the malloc. I would like to know the reason.
Thanks in advance,
YTR
| |
by: MackS |
last post by:
In C89 can I safely do the following
void function(void *p)
{
FILE *fp = p;
/* ... */
return;
}
|
by: harvie wang |
last post by:
Hi,
I want to implement a common Form with special interface, such as MovePoint(double,double).
I create a interface first:
namespace ABC.Test
{
public Interface IMyWindowInterface
{
void MovePoint(double,double);
}
}
|
by: William S Fulton |
last post by:
I'm looking for the name of the following casting style in order to do
some reading around on it and why it is sometimes used.
unsigned long long ull = 0;
void * ptr = 0;
ull = *(unsigned long long*)&ptr;
As opposed to the more usual casting:
|
by: sophia.agnes |
last post by:
Hi ,
I was going through peter van der linden's book Expert C programming,
in this book there is a section named "How and why to cast"
the author then says as follows
(float) 3 - it's a type conversion and the actual bits change.
if you say (float) 3.0 it is a type disambiguation,and the compiler
can plant the correct bits in the first place.some people say that
|
by: alex.j.k2 |
last post by:
Hello all,
I have "PRECISION" defined in the preprocessor code
and it could be int, float or double, but I do not know in the
code what it is.
Now if I want to assign zero to a "PRECISION" variable,
which of the following lines are correct:
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
| |
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
| |
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |