Search:

Type: Posts; User: Norm

Search: Search took 0.12 seconds.

  1. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    Add more printlns to show the values of the variables as they are changed. For example print out the value of line immediately after each readLine() statement.
  2. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    The problem is the scope of the definition for the variable. The definition is only known within the enclosing pair of {}s. You need to move the definition up until it is at the same nesting level of...
  3. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    Again check for correctly matching {}s
  4. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    Definitely, yes.

    Where is the Level variable defined? If it is from the Java SE classes, read the API doc to find out what package it is in and add an import for it.
  5. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    What is on or before line 18?
    Make sure the {}s are correctly paired.
  6. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    You need to tell the compiler where to find the definitions for those classes. You can use an import statement to do that.
  7. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    Please copy and paste the full text of the errors here if you want help with them.
    Why are you using Level and Logger?
  8. Replies
    16
    Views
    2,030

    Re: new use of bufferedreader, uncharted territory

    Why do you think there is anything wrong with the code?
    Can you explain?
Results 1 to 8 of 8