We will continue working on our digit class, moving ever closer to an eventual object-oriented project (but not quite yet)
This week's project is related to sam0, only instead of encoding/decoding text using a caesar cipher, your task in cbf0 will be to unscramble an image file.
Week 10
We will continue with our Object-Oriented endeavors this week, finishing up/reviewing classes, and then moving on to inheritance.
The first Object-Oriented project may get underway
Week 9
We started on Object-Oriented Programming in C++
Secret Agent Messaging (sam0) is the new project
Week 8
I haven't heard a peep from anyone all break… hopefully that means lots of people are having fun drawing a circle of squares.
The next project to tide us over: another mental math trick. afn0 makes for a great party trick.
Break Week
I evaluated mbe1! We are currently up-to-date on our projects.
A bit of a surprise to be sure… less than half the class submitted it. mbe1 was a bit more involved, so I wonder if the outcome was due to expectational procrastination. Let this be a lesson to you for future projects.
I went and scoured through all the opii and updated any records I had.
Warning grades go out today… be advised.
Week 7
We should be wrapping up our initial discussion of functions, and then explore some C library stuff, specifically image creation/manipulation with gd
Week 6
We're starting to get to the point where the volume of concepts and coding possibilities at your disposal are considerable. The only way you will do well is if you take the time to play and review and otherwise expose yourself to the concepts and ideas that such things enable. Do not just come to class and type in whatever code we work on… you MUST tinker with things outside of class too. Experiment, break things, try solving related problems.
Barring any questions, we'll be exploring functions this week, the last major concept to cover in C. Then, we'll take a little time exploring all these concepts in combination, before moving on to C++.
Week 5
Week 5 hits a few milestones:
This week effectively marks the 1/3 waypoint of the semester. Can you believe it?
Fall begins on September 23, at 4:21 A.M. … so be sure to enjoy what remains of summer!
General observations:
rushing begets confusion and stalled progress. Be it rushing due to procrastination, or rushing due to not putting adequate amounts of time into understanding, it will hurt you if you do not spend the appropriate amount of time to learn the new concepts and to become increasingly fluent with them.
I cannot stress this enough: you must take the time to practice this material.
Week 4
Our programming capabilities grow with each passing class, each passing week.
Barring any questions, we'll be proceeding onto to loops this week:
for() - counting (aka “automatic counter”) loops
while() - top driven relational loops
do while() - bottom driven relational loops
arithmetic shortcuts:
++ - increment by 1 (comes in both pre- and post-increment varieties)
– - decrement by 1 (comes in both pre- and post-increment varieties)
+= - increment by provided value
-=, *=, /=, %=
Week 3
We explored:
pointers
negative numbers
if statements
else if
else
compound if statements
relational operators
and how properly organizing them can be beneficial
viewed assembly conversion of our C programs (-S argument to gcc)
binary masks, logic
Week 2
Explored input with scanf()
Expressed values according to different schemes (octal, signed/unsigned decimal, hex, ASCII)
Started looking at pointers, including double pointers
Week 1
Welcome! I've wrapped all the initial activities into one project, cci0, that I'd like you to perform by the given deadline (by 11:59:59pm / 23:59:59).
Get familiar with logging into the pod systems, and once there:
open up a terminal
log that terminal onto Lab46 for class work and attendance
Get familiar with how to log onto Lab46, and once on:
change to your src/ subdirectory
create/edit .c files (such as hello.c), and how to save/exit
compile the C program (.c file(s)) into an executable with gcc
execute the compiled C program (the executable) by specifying a path: ./program_name
haas/fall2015/cprog/projects.txt · Last modified: 2015/11/10 13:15 by wedge