Carey Brown

// LINE 1. CODE TO DETERMINE WHETHER USER INPUT IS OUT OF BOUNDS GOES HEREAssuming that this is part of your requirements, this calls for an 'if' not a 'switch'. Do you know what the correct range is?

        int numberOfAngles=3;// LINE 1. CODE TO DETERMINE WHETHER USER INPUT IS OUT OF BOUNDS GOES HERE         String userInputStringOfAngles;            switch (numberOfAngles){           case '1' : userInputStringOfAngles="3"               break;           case '2': userInputStringOfAngles="4"                               break;           case '5':userInputStringOfAngles="5"                             break;         default :            System.out.println("Invalid input");                // LINE 2. SWITCH CODE TO PRINT CORRECT "SHAPE" MESSAGE BASED ON USER INPUT GOES HERE                          }Why do you have 1, 2, and 5 when your requirements state 3, 4, 5?

Daniel Demesmaecker wrote:You can also just place the codetags first and pasted your code between them...

Nice tip. Hadn't thought of that =)

I see you attempted to use the Code tags. For them to work properly you must first have the code highlighted. You can do this by dragging the cursor over the code. If you have a very long block of code then sometimes this doesn't work, so an alternative way to highlight the code is to scroll up to the top of the code and single left click just before the first character, and then scroll down to the end of the code and after the last character do Shift+left click. This should now highlight the code and you can now click on the "Code" button. ALWAYS verify by clicking the "Preview" button at the bottom of the edit window.

I'll fix it for you this  time.

What happens if you rename the file to "x.java" ?

When I google Krasomowca it shows that the 'o' is accented. Is it possible that the file name has this accent?

Type in
javac -version
to see what the computer thinks your version is

Whenever you have compile or run time errors/exceptions, post the complete error message here. There's often useful info in the message.

You are struggling with Scanner and how you expect console input to behave. With console input each data item must be followed by pressing the Enter key. Because Scanner was written to also deal with reading text files they are designed with the ability to put multiple values together on one line. Console input must explicitly forbid this, a task the Scanner was not designed to do.

It is also useful to create some helper methods for console input which encapsulates this concept in order to simplify your application code. Here's an example. The first two promptXXX() methods shouldn't be used but are here so that you can compare their behavior to what you are currently doing.

Note that the constant CONSOLE is created once and used everywhere. Only one Scanner built from System.in should ever be created.
import java.util.Scanner; public class ScanAge { public static final Scanner CONSOLE = new Scanner( System.in ); public static void main( String[] args ) { System.out.println( "AGE: " + promptInt( "Type your age: " ) ); System.out.println( "GPA: " + promptDouble( "Type your GPA: " ) ); } // // These "work" but I don't like them. Console input should // expect each data item to be followed by a new-line but // these don't behave that way. // private static int promptInt2( String prompt ) { System.out.print( prompt ); while( !CONSOLE.hasNextInt() ) { CONSOLE.nextLine(); System.out.println( "Not an integer, please try again." ); System.out.print( prompt ); } int i = CONSOLE.nextInt(); CONSOLE.nextLine(); // flush new-line return i; } private static double promptDouble2( String prompt ) { System.out.print( prompt ); while( !CONSOLE.hasNextDouble() ) { CONSOLE.nextLine(); System.out.println( "Not a number, please try again." ); System.out.print( prompt ); } double d = CONSOLE.nextDouble(); CONSOLE.nextLine(); // flush new-line return d; } // // These work correctly for console input. Entering a // new-line after each data item is required. // private static int promptInt( String prompt ) { while( true ) { System.out.print( prompt ); try { return Integer.parseInt( CONSOLE.nextLine().trim() ); } catch( NumberFormatException e ) { System.out.println( "Not an integer, please try again." ); } } } private static double promptDouble( String prompt ) { while( true ) { System.out.print( prompt ); try { return Double.parseDouble( CONSOLE.nextLine().trim() ); } catch( NumberFormatException e ) { System.out.println( "Not a number, please try again." ); } } } }

line 6 will leave a pending new-line. You can call nextLine() immediately after that to flush the new-line.

Yes, but to flush out the non-int you could call next() or nextLine(). Different behavior though.

It depends. If someone enters
ABC 42
Of course you want to throw away ABC, but do you also want to throw away the 42 ?
If so then call nextLine().

import static java.lang.System.*; public class Box { private String word; private int num; // don't need this public Box() // Don't need this {   } public Box(String s) // not doing anything with 's' {   } public void setWord(String s) // don't need this { word = s; } public String toString( ) {  num = word.length(); // dont't need this  for(int num=0; num<=word.length(); num++)  {    return word; // first time it gets here it returns and doesn't                               // continue looping  }          // no return here          // compiler has no way to know other return is the only way out } }

In you body you need to call
console.next();to flush out the non-int.

Your requirements don't specify whether the client or the server is responsible for the persistence of the balance. The way you've got it the client is responsible, but if the client gets closed you lose the balance unless you store it in a database or a file. If the server were to be responsible then the server should store it in a database or a file. The main difference being do you have one database (or file) per client or one for the server and therefore be able to store the balance for all users. If the server is responsible then a user id of some sort would be needed in order to retrieve the balance specific to that user.

The use of a Thread should be used regardless, the ServerSocket and accept() method are based on that model. Whether a client opens a connection once and maintains it for the life of the client, or the client re-connects for each "send" is up to you.

P.S. When you post please don't quote a previous post unless it is not obvious to which post you are referring. It just adds bulk to the thread without adding more information.