edaena / edaena-cs371p-darwin Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/edaena-cs371p-darwin
Automatically exported from code.google.com/p/edaena-cs371p-darwin
The UML diagram.
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:38
Creatures have been placed correctly on the grid.
After the 1000 moves, our final board does not look like other final boards
from the public repo.
Original issue reported on code.google.com by [email protected]
on 3 Apr 2012 at 5:59
Use Doxygen to document the interfaces.
The above documentation only needs to be generated from Darwin.h.
Comment each function meaningfully.
Use comments only if you need to explain the why of a particular implementation.
Choose a coding convention and be consistent.
Use good variable names.
Write readable code with good indentation, blank lines, and blank spaces.
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:37
If we call print_board before making a move we get a segfault.
Original issue reported on code.google.com by [email protected]
on 30 Mar 2012 at 9:17
Set up a private Git repository at Assembla:
https://www.assembla.com/code/<cs-username>-cs371p-darwin/git/nodes/
Invite the grader to your repository:
Alon Farchy (afarchy)
Oliver Jensen (ojensen5115)
Commit at least 5 times.
Commit once for each bug or feature.
If you cannot describe your changes in a sentence,
you are not committing often enough.
Write meaningful commit messages and
identify the corresponding issue in the issue tracker.
Create a log of the commits.
Push frequently.
It is your responsibility to protect your code
from the rest of the students in the class.
If your code gets out,
you are as guilty as the recipient of academic dishonesty.
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:35
Set up a public issue tracker and wiki at Google Project Hosting:
http://code.google.com/p/<cs-username>-cs371p-darwin/
Issue Tracker
Track the 8 deliverables on this page.
Track bugs and features, both open and closed.
Categorize, prioritize, and describe each issue adequately.
Track at least 5 more issues in addition to the 8 issues on this page.
Wiki
Describe the design of the algorithm.
Write at least 30 lines of description.
Use bullet points where appropriate.
In general, write grammatically correct, typo free, clear English.
Have someone else read what you wrote and critique it.
Write neatly.
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:34
There are more rovers after 1000 iterations than best.
Original issue reported on code.google.com by [email protected]
on 3 Apr 2012 at 6:01
There is an error being produced in the add_creature method of the board class.
error: 'creature' has incomplete type
add_creature(Creature creature, int r, int c);
Original issue reported on code.google.com by [email protected]
on 29 Mar 2012 at 8:29
Push and pull the acceptance tests to and from the grader's repository.
Prepend <cs-username>- to the file names at Assembla.
Reach consensus on the acceptance tests.
Use Valgrind.
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:36
rand() gives row major order int for the position of a creature. We are
dividing by 72 to get the row # and the modding the row by 72 to get the column
number. This is giving us the diagonal.
Original issue reported on code.google.com by [email protected]
on 2 Apr 2012 at 6:22
Fill out the grader's Google form:
Alon Farchy
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:38
Creature move says the species pointer is null.
Original issue reported on code.google.com by [email protected]
on 29 Mar 2012 at 11:37
The grader will set up a public Git repository at Assembla:
Alon Farchy
https://www.assembla.com/code/ojensen-cs371p-darwin/git/nodes/
Write unit tests before your write the code.
When you encounter a bug, write a unit test that fails,
fix the bug, and confirm that the unit test passes.
Write at least 3 unit tests for every function.
Tests corner cases and failure cases.
Name tests logically.
Push and pull the unit tests to and from the grader's repository.
Prepend <cs-username>- to the file names at Assembla.
Reach consensus on the unit tests.
Use Valgrind.
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:36
Use assert to check pre-conditions, post-conditions, argument validity,
return-value validity, and invariants.
Worry about this last, but your program should run as fast as possible
and use as little memory as possible.
Original issue reported on code.google.com by [email protected]
on 27 Mar 2012 at 10:37
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.