This is the home page for CS253, Problem Solving with C++,
a CSU Computer Science class.
Click on the sidebar, on the left, for other class pages.
According to Wikipedia, the last declaration of war was in 1942, against Bulgaria, Hungary, and Romania. Congress never declared war against Korea, North Vietnam, Afghanistan, or Iraq.
The review session for the final exam will be Tuesday 1:30-3:30ᴘᴍ, in CSB 215.
The read-only solution to HW5 is here.
They are located at the bottom of the HW6 page.
Please see me during office hours or send me an email if you have any questions or concerns.
A read-only solution to HW6 is available here.
They are located at the bottom of the HW5 page.
Please double check your HW5 grades. If you have any questions or concerns, please see me during office hours or send me an email!
Please see me during Office Hours or email me if you have any questions!
insert is now pair<iterator,bool>.
> When the "Display the schedule for the next/prev week" button is pressed should the program display a week's worth of events or a day's worth of events for the day a week from where you currently are?
That button was poorly described—just go forward a week and display a day’s worth of events.
> When we display an error message for a bad line in the file, do we terminate the program after the error box comes up?
A bad line does not end your program. Complain and keep going.
> If the file .schedule can’t be found, what do we do?
Same as above—complain and keep going. You won’t have any data to display, but that’s ok.
> I have a memory leak!
Due to an error in gtkmm, you are not to worry about memory leaks.
valgrind consistently reports memory leaks in gtkmm programs,
so the leaks must be in code that we can’t control.
> Should each event be a line of text, in HW4 style?
That would be sufficient.
> Should each event be a widget?
If you want to.
> When the event spans multiple hours how/should that be indicated?
Show the start and end times. In fact, you must always show the start and end times.
> When events overlap how/should that be indicated?
It shouldn't.
> Will the year range for this assignment will be the same as in HW4? (1900-2100)
Yes.
> Is it OK to trim the date information from the displayed events, since they’re all the same date?
Yes. Remember that it must be clearly indicated which day we’re looking at, even if no events are visible.
They are located at the bottom of the HW4 Assignment Page
Please see me or email me if you have any questions!
They are located at the bottom of the HW3 Assignment Page
With regard to exceptions thrown in HW4, 42 is an int.
Due to the intervention of your beloved GTA, the late period for HW4 had been extended 24 hours, until 2:00ᴘᴍ Friday.
My solution to HW3 is availble: Freq.h and Freq.cc. They’re for viewing only, not for saving.
Please see or email me ASAP if you have questions!
In HW4, the parameter mon in the numeric version of .add()
is to be interpreted as 1=Jan, 2=Feb, 3=Mar, ..., 11=Nov, 12=Dec.
Similarly, the day parameter is 1-based, not 0-based.
Several students have asked if there is a limit to the length of an event. My (unstated) intention was that events don’t go past midnight. That is, an event is limited to being entirely on a single day. Hence, no event can be more than 24 hours, and an event that starts at 23:00 can be at most an hour long. However, you don’t have to check for this. We will only test your code with events that don’t go past midnight.
Also, the .print() method should be const. I had it correct
in ScheduleBase.h, but wrong in the writeup.
Mr. Bernard pointed out that the documented signature for .add() was
different from what was in ScheduleBase.h. I’ve fixed ScheduleBase.h.
I’ve updated the HW4 description again:
ScheduleBase.h and ScheduleBase.cc are now provided.
.size() method is now const.
I’ve updated the HW4 description. Strings given to .add() and +=
now include a weekday and a year, and you must do error-checking on both.
Something’s come up, and Jack won’t be able to be there for his office hours on Friday, October 8th. Sorry!
To be clear: in HW3, max_size is a maximum size.
If, for example, max_size is 3, then your code should process sequences
of length 1, length 2, and length 3. When operator<< is invoked,
the sequences of length 1 will be printed, in sorted order,
then the sequences of length 2, in sorted order,
then the sequences of length 3, in sorted order.
test files used for grading hw2 have been posted at the bottom of the Homework 2 assignment page.
| 2 | 3% | ||
| 3 | 7% | ||
| 4 | 3% | ||
| 5 | 6% | ||
| 6 | 13% | ||
| 7 | 10% | ||
| 8 | 18% | ||
| 9 | 25% | ||
| 10 | 7% | ||
| 11 | 3% | ||
| 12 | 3% | ||
| 13 | 1% |
HW3 is now available.
According to Wikipedia, there are twenty-three countries on the North American continent:
Antigua and Barbuda Bahamas Barbados Belize Canada Costa Rica Cuba Dominica Dominican Republic El Salvador Grenada Guatemala Haiti Honduras Jamaica Mexico Nicaragua Panama Saint Kitts and Nevis Saint Lucia Saint Vincent and the Grenadines Trinidad and Tobago United States
If you feel you were incorrectly penalized for extraneous output such as prompts, error messages, or debug statements, please see or email me ASAP!
In HW2, you do not have to treat reading from the terminal differently
than reading from anywhere else. Just read from cin.
In HW2, newlines are to be ignored. However, a letter pair will not cross a line boundary. See the third example in the assignment.
Jack will be in Michigan September 13–14 for his mother’s 90th birthday, and so will not be in his office Tuesday morning.
Examples of using getopt:
To check your grade, log on to a cs department machine and type into a terminal ~cs253/bin/grade HW1. Any questions? See me during my office hours or shoot me an email.
To check your grade log on to a cs department machine and type into a terminal ~cs253/bin/grade HW0
My hours are now available on the Syllabus. Please note that the days and times may change in the near future.
A student asked if -Wextra implies -Wall.
A good question—this indicates that it doesn’t:
% cat c.cc main() { } % g++ c.cc % g++ -Wall c.cc c.cc:1: warning: ISO C++ forbids declaration of ‘main’ with no type % g++ -Wextra c.cc %
checkin should work nowI screwed up the permissions on a log file, which prevented you from checking in HW0. Sorry! It should work as of 5:45ᴘᴍ Monday.
|
Modified: 2010-12-16T18:16 User: Guest Check: HTML CSSEdit History Source |
Apply to CSU |
Contact CSU |
Disclaimer |
Equal Opportunity Colorado State University, Fort Collins, CO 80523 USA © 2015 Colorado State University |
|