EoCE's have been deployed to your Opus. Look there (be sure you're signed in to the wiki, otherwise it will not show up!). The project page link here will now lead to an empty page.
I put up a hints page (last link in projects listing above), which I will endeavour to paste in some useful responses I have given to some excellent questions asked in relation to the EoCE. Be sure to check it out.
Topic for this week will be polymorphism/virtual functions.
Sample code placed in: /var/public/cprog/spring2015/polymorphism/ on lab46.
Week 11
I have put together the End of Course Experience (EoCE) for the class. This is your final assigned project for the class (and is assigned in lieu of a final exam). When I finish all the other EoCEs for my other classes, the project link above will disappear, and your pertinent EoCE(s) will appear at the bottom of your Opus (so when it disappears from here look there).
It is open resource, but closed person.
You are expected to work on this by yourself (you may ask me for clarification).
It, along with anything else outstanding that you'd like to receive credit for (even if just for consideration), please have submitted to me in the proper places by 4:30pm on Thursday, May 14th, 2015.
We'll be exploring the next item on our Object-Oriented explorations: inheritance
Week 10
Started exploring Object-Oriented Programming using C++
I unveiled cbf0, a project aimed at helping you better understand binary data, and its manipulation, to aid in your on-going hex editor creation efforts.
Talked about structs.
Week 7
Some people really appeared to benefit from the extra time on mbe1; others are still a mystery (I thrive on questions).
I have extended the afn0 project by a week to help everyone get caught up.
Week 6
Went over the debugger, fielded some questions on syntax, function, and array usage
extended current project deadlines
Week 5
I've had a few good questions with respect to the mbe1 project, so I know at least a few of your are putting in good, solid effort.
This week's project is now available- afn0, somewhat simpler in solution than last week, although perhaps more abstract due to organizational requirements. Also perhaps easier since it requires many of the same core skills you had to use in the mbe1 project.
Week 4
On the heels of our last exciting project, and with our first break coming up, I've put together a project that should offer you plenty of opportunity to improve your programming capabilities.
mbe1 takes our multiply by eleven program and expands its functionality, for numbers of up to 8 digits.
we'll make the program more efficient through the use of arrays and loops
again, take time, try things out, experiment and play. There'll be some mental obstacles with this stuff, and the only way to get past them is to work through them.
Week 3
Our mental math explorations continue! This week we will explore multiplying and 1-, 2-, or 3- digit number by 11
We'll also learn how to let the computer make decisions, using if statements
Week 2
I've had some good conversations with various individuals on aspects of C over the past week.
You can and are encouraged to clone your BitBucket repository onto lab46 so you can add/commit/push work you do in the lab to it for Joe's consideration.
Should you need assistance, an increasing number of people have been getting this set up
Kyle, our excellent LAIR tutor, can also be of immense value in helping you to achieve success
The next C project has been unveiled, mms0, which will let us explore the modeling of a mental math trick in C code (what better way to solve a problem– to learn a new skill and then apply it to code!)
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/or LAIRstations, 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
