|
Welcome to the Lab-test Environment
|
|
During
the test,
you will not be able to access your regular home directory,
access, receive, or send e-mail, print, or access the Internet.
The lab tests are closed-book and no aids are allowed.
At the end of your test session,
this machine will be converted back to a standard, unrestricted
Prism Lab machine.
At this time, any files written by you during the test,
except those that have been submitted,
will not be recoverable.
Make sure you submit your code
before the end of the test.
(Instructions to submit your code are below).
If you do not submit your work on time,
you will receive a grade of zero.
(There are no exceptions.)
|
|
Instructions
You have the lab period,
80 minutes,
to complete this lab test.
The computers will automatically shutdown at the end of the time
(e.g., 6:20pm),
warning you several minutes in advance.
No additional time will be provided,
so you must submit your work prior to this;
otherwise, there will be no way to recover it (it will be lost),
and you will receive a grade of zero (no exceptions).
You are encouraged to submit often during the test.
Note that newer submissions overwrite older ones.
Your program will be marked for good style,
as well as for running correctly
(producing correct output in the correct format).
|
|
Submitting Your Work
When
you submit a file,
you should include at the top of the file your name (surname, given name)
and your Prism lab login.
These should be placed in a comment so that the file will compile.
Note that files which do not compile will receive a large penalty
when marked,
no matter how small the error that prevented compiling.
Submit the class Palindrome.java
before the time deadline.
Here is the command to submit your work:
-
%
submit 1020 labtest2W5.00 Palindrome.java
Further details regarding the submit command can also be
obtained by typing man submit.
Once again, you are encouraged to submit regularly.
Newer submissions simply overwrite older ones.
Unlike eCheck assignments,
there is partial credit possible.
If you are able to finish all aspects of the program
(for example, say, input validation was requested
but you did not do this),
you should still submit it.
|
|
Useful APIs
Here
are the common APIs that you may access:
|
|
|
|
Write
a Java application called Palindrome.java.
A palindrome is a sentence or phrase that is spelled the same forwards
and backwards (ignoring spaces, punctuation, and case of the letters).
For example, the following are all palindromes:
Was it a rat I saw? |
No lemon, no melon. |
No, sir, away! A papaya war is on! |
Your program should repeatedly prompt a user for a line
of text and determine if the text is or is not a
palindrome. Your program should only consider the letters
in the line (ie. it should ignore spaces, punctuation
marks, and digits) and it should ignore the case of
the letters. The empty line should be considered not
a palindrome. The user should enter the line done
to end the program.
Your output should look exactly like that indicated
in the sample runs below.
Hint: Use a regular expression to remove all of
the non-letter characters from the user input string.
|
|
Sample Runs
Here
is one sample run of a correctly written program.
Note that the text in red is text that the user types.
The text in black is what the program types.
The '%' represents the prompt from the command-line window (shell).
-
% java Palindrome
Type in a sentence followed by the ENTER key:
Was it a rat I saw?
Is a palindrome
Type in a sentence followed by the ENTER key:
No lemon, no melon.
Is a palindrome
Type in a sentence followed by the ENTER key:
No, sir, away! A papaya war is on!
Is a palindrome
Type in a sentence followed by the ENTER key:
1234321
Not a palindrome
Type in a sentence followed by the ENTER key:
Hello there.
Not a palindrome
Type in a sentence followed by the ENTER key:
Not a palindrome
Type in a sentence followed by the ENTER key:
done
%
|
|
Coding
You
should use good programming practises
as described in the textbook,
and your code should conform to the style guide in the textbook.
You should comment at least minimally,
as by the guidelines.
You should not use any features of Java not covered
in the first six chapters of the text.
There will be some deduction if you do.
|
|
|
|