[FUXAS]

I've written This code to read from file :

package Javaapplication 9;

import java.io.File;
import java.io.FileNotFoundException;
import java.util.Scanner;

public class Main{
  public static void main(String[] args) throws FileNotFoundException {
    Scanner scanner =
      new Scanner(new File("C:/Users/F/Desktop/textfile.txt")).useDelimiter("\\Z"); /* z - failo pabaiga*/
    String skaiciai = scanner.next();
    System.out.print ("skaiciai yra: "); /* isvedam i ekrana uzrasa "skaiciai yra" */
    System.out.println (skaiciai); /* isvedam skaicius, kurie yra faile*/
    scanner.close();
  }
}

Then, I need to sum numbers from that textfile.txt.. And I have no idea how to make a massive to sum them..
For example : in file numbers are 12156, sum of them is : 15..

This post has been edited by FUXAS: 06 March 2010 - 10:54 AM

[javabie]

you could use BigInteger class...

have a look at this...
http://java.sun.com/...BigInteger.html

[macosxnerd101]

Assuming the numbers are separated by a delimiter, say whitespace for example, you can read them all in using the Scanner's nextInt() method and sum as you go. Or if they are all as one String, you will have to go through character by character in the String and sum. Note that '1'-'9' as chars are equivelant to 48-57 as ints.

[zim1985]

macosxnerd101, on 06 March 2010 - 02:10 PM, said:

Assuming the numbers are separated by a delimiter, say whitespace for example, you can read them all in using the Scanner's nextInt() method and sum as you go. Or if they are all as one String, you will have to go through character by character in the String and sum. Note that '1'-'9' as chars are equivelant to 48-57 as ints.

Could he go through character by character and then use the parseInt() method to convert each String number to an int?

[macosxnerd101]

That would work, though knowing the ASCII values for the numerical characters will allow for more memory efficiency, since you would be creating a new String object for each parse.

[zim1985]

macosxnerd101, on 06 March 2010 - 03:26 PM, said:

That would work, though knowing the ASCII values for the numerical characters will allow for more memory efficiency, since you would be creating a new String object for each parse.

This is true. My way seems like the quicker, easier, less efficient way to go...

[macosxnerd101]

I've got to disagree here on the quicker and easier part. It will still take no fewer lines of code (and probably more depending on implementation) than my solution, and it won't run any faster. It just eats up a little more memory.

[zim1985]

macosxnerd101, on 06 March 2010 - 07:31 PM, said:

I've got to disagree here on the quicker and easier part. It will still take no fewer lines of code (and probably more depending on implementation) than my solution, and it won't run any faster. It just eats up a little more memory.

All depends on how your mind works I guess...thought process is (nearly) everything in programming.

I just thought mine would be easier because it doesn't involve having to know ASCII values. I'm not saying this is hard to get the ASCII values or anything...

This post has been edited by zim1985: 06 March 2010 - 09:36 PM

[macosxnerd101]

Algorithmically speaking, you are correct. However, a big part of efficiency analysis is understanding the drawbacks when it comes to implementation.

As for looking up things when programming, get used to it. Not a day goes by when I do not look at the API, ASCII table or some other reference when helping other DICs. A big part of programming is understanding your tools, which comes from looking things up a lot of the time.

[zim1985]

macosxnerd101, on 06 March 2010 - 07:41 PM, said:

Algorithmically speaking, you are correct. However, a big part of efficiency analysis is understanding the drawbacks when it comes to implementation.

As for looking up things when programming, get used to it. Not a day goes by when I do not look at the API, ASCII table or some other reference when helping other DICs. A big part of programming is understanding your tools, which comes from looking things up a lot of the time.

I know what you mean about looking stuff up. Today I was helping with some Swing stuff, or maybe it was yesterday, and I had to scroll through the API, find the method and justify. I know what you mean.

You have no idea how much I learned just in the past week or so I have been here. So many new ways of look at problems have come to me now that I have seen so many different ways of solving problems. To more I can absorb, question, and attempt the better I seem to get at seeing what is wrong and figuring stuff out. I would be lying if I said reading your posts, dogstopper's, and eric.price's posts (among a few others whose names have escaped me) haven't helped.

Now I'm not quite sure how I got off-topic, but yeah. I'm always open to other viewpoints and looking stuff up to help and learn...