Structures question: How do I show information inside a structure?

How do I show all of the variables + their single structure names that are within a structure type to the user?

first, your post is quite confusing to difficult to understand.

you use '.' (period) to access members of the struct. if the struct is a pointer you use '->' ('indirect member selection' operator). to show the information, you use the same method you would for showing any other information.

Fixed; it should be easier to understand, now, :-).

Same way you would a class. Write a meathod or function that prints everything that you need out.

There is no automated way to print the name and value of all struct members: the name is no longer available at runtime.

Just out of curiosity, would there be a way of writing a program such that if it were compiled into a debug version (i.e. with the symbolic tables embedded), the program be able to look into its own symbolic table?

I mean, a vague idea would be

Code:

---

int main(int argc, char* argv[])
{
      FILE* f = fopen(argv[0], "r"); //so here you'd pass its own self as an argument
      look_in_the_symbolic_table_of_the_file_,_format_it_and_print_it_out(f);
}

---

argv[0] doesn't necessarily contain the filename of the program in question.

> the program be able to look into its own symbolic table?
Theoretically, yes. Examples of such programs are called debuggers.

But if you only have one or two such structures, then its much easier to roll the code yourself.

Quote:

---

argv[0] doesn't necessarily contain the filename of the program in question.

---

Is it shell specific? At least in Bash and Windows, I think you always get the name of the executable or script.

It always includes the filename, but it may also include the path or a partial path.

And the filename in question might specify a symbolic link.

Oh, and the filename is looked up in the PATH, whereas fopen doesn't look, which means that if you don't call the program with an explicit path, it won't find the executable in the fopen call.

Right, I'd forgotten that executables have to be in the path to run. I guess you could do some kind of combo with getenv and searching for the file in each of the path directories.

Symbolic links... Can't see any way around that. Oh well, recursive self-reference is always interesting.