Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exercise 38: Scope Rules in C ("scope_rules") ("Chapter 4.4") #109

Open
danwritecode opened this issue Jun 5, 2024 · 2 comments
Open

Exercise 38: Scope Rules in C ("scope_rules") ("Chapter 4.4") #109

danwritecode opened this issue Jun 5, 2024 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@danwritecode
Copy link
Owner

Looking for help creating exercise:
Topic: Scope Rules in C
Exercise Directory Name: scope_rules

Note: For Directory Name, refer to the exercises directory to find the correct number to use. It should be close to the number in the issue title but may be slightly off.

Refer to "The C Programming Language" book, Chapter 4.4 for more information.

Contribution instructions: https://github.com/danwritecode/clings?tab=readme-ov-file#contributions

@danwritecode danwritecode added the help wanted Extra attention is needed label Jun 5, 2024
@sleaper
Copy link
Contributor

sleaper commented Jul 29, 2024

For this exercise (chapter 4.4) and exercise #108 (chapter 4.5), we must compile multiple .c files into a single program to demonstrate the principles of extern and header files. Also, we will need it in the future for maybe more complex exercises.

I propose that all .c files in the exercise folder with a suffix such as ex (for executable) will be compiled into one program. For now, I will skip these two chapters. If anyone has another idea on how to approach this, please let me know.

@danwritecode
Copy link
Owner Author

@sleaper let me think about it a bit, but your proposal makes sense at a surface level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants