When writing and submitting your assignments follow these requirements:
Name your Eclipse project with your Network login, an underscore, ‘a’ (for ‘assignment’, then the assignment number: login_en.zip. For example, if the user barn4520 submits Assignment 1, the name should be: barn4520_a01. Give your .zip file the same name when exporting your project. The project above would be eported in a .zip file named barn4520_a01.zip. Use only Eclipse’s built-in archive capability to create these .zip files. No other format will be accepted.
Some assignments consist of multiple Eclipse projects where one project references another. Use the same naming scheme for all your projects. Thus, a project named data_structures should be barn4520_data_structures.
Test your programs thoroughly - show us how it works. Copy the outputs from your testing to a file in your Eclipse/Pydev project named testing.txt. Make sure the tests are well labelled so that the markers know which program the results represent.
If you are asked to provide discussion put this discussion in your Eclipse/Pydev project in a file named discussion.txt.
Put all your programs, testing, and discussion files into one Eclipse/Pydev project.
Zip the entire project using Eclipse and submit the resulting .zip file through MyLearningSpace.
Use the Validate Assignment link to make sure that your project and .zip file are named correctly have have the proper contents. Improper assignment submissions are given a grade of zero.
Marks will be deducted from any questions where these requirements are not met.
You may use any code or libraries provided as a solution to previous labs or assignments if your own code or libraries are incomplete or incorrect.
Use your code from Lab 4 : Lists and given the code in list_array.py, complete the implementation of the following methods:
identical remove_many __getitem__ clean: you may not use Python list segments intersection union insert_front remove_front combine split split_alt
NOTE: your code must work at the lowest level of the ADT.
Test all the List methods with Movie objects. (Don’t forget to test them with an empty list!). Put your test program in q1.py and the test results in testing.txt.
You may test your code at CP164: List Testing. (WLU Network login required.)
Given the code in sorted_list_array.py, complete the implementation of the following methods:
remove index find peek identical remove_front remove_many count: you may not use the Python count method min: you may not use the Python min method max: you may not use the Python max method __contains__: you may not use the Python in operator __getitem__ clean: you may not use Python list segments intersection union
NOTE: your code must work at the lowest level of the ADT, and make use of the fact that the list is sorted. Thus, most of these methods should be implemented differently than similar methods in the previous question.
Test all the SortedList methods with Movie objects. (Don’t forget to test them with an empty list!). Put your test program in q2.py and the test results in testing.txt.
You may test your code at CP164: Sorted List Testing. (WLU Network login required.