[TheEmpty]

Add @Override notation?

[Qasim]

Sometimes IDE's just make weird errors like that, don't they? I'm not too sure but it might also be because your out classes have different paramters yet your in class have the same parameters.

[NeilHanlon]

Pretty sure just overriding it will work perfectly. That, or just redefine the in method.

[TheEmpty]

Qasim, on 07 May 2012 - 04:17 PM, said:

Sometimes IDE's just make weird errors like that, don't they? I'm not too sure but it might also be because your out classes have different paramters yet your in class have the same parameters.

Nope, if an IDE for a compiled language complains, it means the compiler is complaining. Eclipse uses JRuby to instantly compile your code and see if the compiler complains.

[ianonavy]

The important factors of a Java method declaration are the name and parameter types. Even though both

in

methods return different types, they have the same name and have the same parameter types, so the Java compiler does not know the difference between the two.

I recommend doing it like this:

/**
 * Test class used as an example for Quinn.
 */
public class Test {
    Scanner scanner;
    
    /**
     * Constructor initializes the scanner to system input.
     */
    public Test() {
        this.scanner = new Scanner(System.in);
    }

    /**
     * Reads the next integer from the scanner with a prompt.
     * @param prompt the prompt to ask the user
     */
    public int inputInt(String prompt) {
        out(prompt);
        return this.scanner.nextInt();
    }

    /**
     * Reads the next string from the scanner with a prompt.
     * @param prompt the prompt to ask the user
     */
    public String inputString(String string) {
        out(string);
        return this.scanner.next();
    }

    /**
     * Shortcut to the System.out.print.
     */
    public void print(Object object) {
        System.out.println(object.toString());
    }
}

Differences:

• javadoc comments
  
• generic "Object" parameter for print; may not work with primitives, so you'll have to overload it
  
• differently named input methods (just like the Scanner class)

Hope it helps (and compiles because I didn't test it.)

[TheEmpty]

ianonavy, on 08 May 2012 - 08:54 AM, said:

The important factors of a Java method declaration are the name and parameter types. Even though both

in

methods return different types, they have the same name and have the same parameter types, so the Java compiler does not know the difference between the two.

ack didn't see that, but yup +1.

Java method signatures are method name + params.

[Sephern]

Yeah, you have to have either a different name or different arguments. The reason being that Java won't know what method you're calling otherwise. For example, you could do something like this

public Integer someFunc(int a, int B)
{
    //do something
}

public String someFunc(int a, int B)
{
    //do something
}

public static void main(String[] args)
{
   Object myVar = someFunc(1, 2);
}

Which function are you calling? Technically there's 2 functions which match your call, and both of them return Objects...

[Quinn]

I realized what Sephern said after a thought about it a little more, and later went with the same idea that Ianonavy had.

[ianonavy]

ThatRailsGuy, on 08 May 2012 - 09:40 AM, said:

ack didn't see that, but yup +1.

Java method signatures are method name + params.

Off topic: You always say +1 but never actually give me reputation. xD I've noticed that on multiple occasions now.

[TheEmpty]

ianonavy, on 08 May 2012 - 03:34 PM, said:

Off topic: You always say +1 but never actually give me reputation. xD I've noticed that on multiple occasions now.

Sometimes I do, sometimes I don't Generally if I say something I don't.