-
-
Notifications
You must be signed in to change notification settings - Fork 202
Pacman Rules concept exercise #1081
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
base: main
Are you sure you want to change the base?
Conversation
While I go away and learn about |
Now I'm confused. I let |
You should be able to have GitHub do it for you by leaving a comment with this in the body: /format See: c/.github/workflows/format-code.yml Line 11 in 37a5a6e
|
Looks like this may not work for forks |
For now just ignore it and I can format it on my Linux machine prior to merge. |
Thanks. I'm obviously not doing everything right on my Linux machine, so it would be good to understand this at some later point. |
More than likely it's a small difference related to the version of |
Better! I installed the |
Could be worse. I first ran a C compiler from 5¼" floppy disks (8086 processor, 640k RAM). That puts 2025 in perspective! |
Draft for now, until there is a policy decision about exemplar/example and header files.
This is a pretty straight ripoff of the C++ version, with a couple of exceptions.
The test file is, of course, new. This is my first experience of Unity, so I'l wait for your comments on what I did wrong.
The
introduction.md
starts with Bob's version in the Booleans concept, but I removed the section on comparison operators: not needed here, and will be covered in the Conditionals concept. I also added a bit on operator precedence from C++, but I'm not sure if it's needed.This passes
configlet lint
andconfiglet fmt
, but I still need to configure my fork to enable manual CI runs (something aboutworkflow_dispatch
that I need to read up on). CI is going to fail in any case.