From: "Mariano Moreyra" <moremari@aca.org.ar>
To: "'Joseph D. Wagner'" <theman@josephdwagner.info>,
'Jeff Woods' <kazrak+kernel@cesmail.net>
Cc: linux-c-programming@vger.kernel.org
Subject: RE: More Pointer Woes
Date: Mon, 29 Dec 2003 10:44:37 -0300 [thread overview]
Message-ID: <000001c3ce11$e74db020$0c81640a@aca.org.ar> (raw)
In-Reply-To: <200312282206.00330.theman@josephdwagner.info>
The problem is that ext2_filsys is a pointer itself to a
struct struct_ext2_filsys
declaration in ext2fs.h:
typedef struct struct_ext2_filsys *ext2_filsys
so, you have a pointer to a pointer to a structure.
I think you should declare fs as an ext2_filsys type, like this:
ext2_filsys fs;
Then you could reference blocksize the way you are doing it in your
code...that is
fs->blocksize
Mariano Moreyra.
-----Mensaje original-----
De: linux-c-programming-owner@vger.kernel.org
[mailto:linux-c-programming-owner@vger.kernel.org]En nombre de Joseph D.
Wagner
Enviado el: Domingo, 28 de Diciembre de 2003 13:06
Para: Jeff Woods
CC: linux-c-programming@vger.kernel.org
Asunto: Re: More Pointer Woes
> "fs->blocksize" refers to a field "blocksize" in a struct or union that
> the pointer "fs" indicates. If "fs" isn't a pointer to a struct (or
> union) then the "->" operator isn't valid. What type is "fs"?
ext2_filsys *fs which can be found in ext2fs.h
> P.S. Did you get this code from an email? Perhaps the ">" came from an
> email quote that didn't get cleaned up and "fs-blocksize" morphed into
> "fs->blocksize". But this looks like a long-shot to me. I expect that
> "fs" is supposed to be a pointer to a struct.
No, I wrote it myself. I've tried:
fs.blocksize
fs->blocksize
*(fs).blocksize (which should be the same thing)
*(fs->blocksize)
*fs->blocksize
*(fs.blocksize)
&(fs->blocksize)
To simplify it:
int blocksize_k = fs->blocksize;
also fails. blocksize is of type int.
Joseph D. Wagner
-
To unsubscribe from this list: send the line "unsubscribe
linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2003-12-29 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 13:45 More Pointer Woes Joseph D. Wagner
2003-12-29 2:32 ` Jeff Woods
2003-12-28 16:06 ` Joseph D. Wagner
2003-12-29 13:44 ` Mariano Moreyra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001c3ce11$e74db020$0c81640a@aca.org.ar' \
--to=moremari@aca.org.ar \
--cc=kazrak+kernel@cesmail.net \
--cc=linux-c-programming@vger.kernel.org \
--cc=mariano_moreyra@aca.org.ar \
--cc=theman@josephdwagner.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).