Return to Question

edited the title, added a tag, and improved formatting.

Source Link

edited May 24, 2015 at 0:20

17.7k
3
28
100

dictionary.c or why do I need dictionary.h?

I am not sure why I need dictionary.hdictionary.h for pset5pset5.

I feel like I can writedefine the functions: check check, loadload, sizesize, and unloadunload in dictionary.cdictionary.c.

dictionary.cdictionary.c is set up so I can writedefine the functions in it without using the header file at all. Why wouldn't I do this and keep all of the code in one file?

dictionary.c or dictionary.h

I am not sure why I need dictionary.h for pset5.

I feel like I can write the functions: check, load, size, and unload in dictionary.c.

dictionary.c is set up so I can write the functions in it without using the header file at all. Why wouldn't I do this and keep all of the code in one file?

why do I need dictionary.h?

I am not sure why I need dictionary.h for pset5. I feel like I can define the functions check, load, size, and unload in dictionary.c.

dictionary.c is set up so I can define the functions in it without using the header file at all. Why wouldn't I do this and keep all of the code in one file?

Source Link

asked May 23, 2015 at 23:31

Brendan Rafferty

dictionary.c or dictionary.h

I am not sure why I need dictionary.h for pset5.

I feel like I can write the functions: check, load, size, and unload in dictionary.c.

dictionary.c is set up so I can write the functions in it without using the header file at all. Why wouldn't I do this and keep all of the code in one file?