From 21f55263c0fd72cfc7e88c8796a95787d2add636 Mon Sep 17 00:00:00 2001 From: zleyyij <75810274+zleyyij@users.noreply.github.com> Date: Sun, 10 Nov 2024 20:41:05 -0700 Subject: [PATCH] vault backup: 2024-11-10 20:41:05 --- .../ECE1400/Chapter 15 Exercises.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/education/software development/ECE1400/Chapter 15 Exercises.md b/education/software development/ECE1400/Chapter 15 Exercises.md index 56b51ea..71f2c06 100644 --- a/education/software development/ECE1400/Chapter 15 Exercises.md +++ b/education/software development/ECE1400/Chapter 15 Exercises.md @@ -10,4 +10,14 @@ b. Function definitions - Functions should only be defined once, and this allows --- -> **3.** We saw that writing `#include ` instead of `#include "file"` may not work if file is one that we've written. Would there be any problem with writing `$include "file` \ No newline at end of file +> **3.** We saw that writing `#include ` instead of `#include "file"` may not work if file is one that we've written. Would there be any problem with writing `$include "file"` instead of `#include ` if *file* is a system header? + +Yes, `""` is a path relative to the current file, whereas `<>` is a path to the system's standard library headers. + +--- + +> **4.** Assume that `debug.h` is a header file with the following contents... +>(a). What is the output when the program is executed? +``` + +``` \ No newline at end of file