Counting character in a string

Question

I'm trying to count how many times a characters occurs in a string, and I'm having a lot of trouble. This is what I have so far:
note: the method call has to be public static int countOccs(char f, String s) and I know that it can be done using only loops, for, charAt, and length () and I want to learn it like that.
[I just chose f, s randomly.]
public class Counting {
public static void main(String [ ] args) {
String s = "Testing";
int countOccs = s.length( );
char [ ] charArray = new new char[counting];
for (int i = 0; i < counting; i++) {
charArray[i]
public static int counting(char f, String s) {
I'm really lost. When I try to define char f = "f" or String s = "Testing" in the method call (public static int counting...) I get messages saying that it has already been declared in the call, but there has been nothing assigned to it. Anyways, I feel really lost. I did find a pattern by looking at my notes from awhile ago, but am having trouble filling out parts of it. (Thanks, memory...) I think the problem comes from having to have the method call be public static int counting (char f, String s). That part confuses me a lot because I want it to print out how many characters of f are in a string, but it doesn't have "void" in it so it doesn't return a value.
for (int i=0; i < s.length(); i++)
char f = s.charAt(i);
if (something that looks at the characters)
do something like count
Edited by: MAresJonson on Feb 6, 2009 6:50 PM

Answer 1

h1. The Ubiquitous Newbie Tips
* DON'T SHOUT!!!
* Homework dumps will be flamed mercilessly. [Feelin' lucky, punk? Well, do ya'?|http://www.youtube.com/watch?v=1-0BVT4cqGY]
* Have a quick scan through the [Forum FAQ's|http://wikis.sun.com/display/SunForums/Forums.sun.com+FAQ].
h5. Ask a good question
* Don't forget to actually ask a question. No, The subject line doesn't count.
* Don't even talk to me until you've:
    (a) [googled it|http://www.google.com.au/] and
    (b) had a squizzy at the [Java Cheat Sheet|http://mindprod.com/jgloss/jcheat.html] and
    (c) looked it up in [Sun's Java Tutorials|http://java.sun.com/docs/books/tutorial/] and
    (d) read the relevant section of the [API Docs|http://java.sun.com/javase/6/docs/api/index-files/index-1.html] and maybe even
    (e) referred to the JLS for "advanced" questions.
* [Good questions|http://www.catb.org/~esr/faqs/smart-questions.html#intro] get better Answers. It's a fact. Trust me on this one.
    - Lots of regulars on these forums simply don't read badly written questions. It's just too frustrating.
      - FFS spare us the SMS and L33t speak! Pull your pants up, and get a hair cut!
    - Often you discover your own mistake whilst forming a "Good question".
    - Often you discover you discover you where trying to answer "[the wrong question|http://blog.aisleten.com/2008/11/20/youre-asking-the-wrong-question/]".
    - Many of the regulars on these forums will bend over backwards to help with a "Good question",
      especially to a nuggetty problem, because they're interested in the answer.
* Improve your chances of getting laid tonight by writing an SSCCE
    - For you normal people, That's a: Short Self-Contained Compilable (Correct) Example.
    - Short is sweet: No-one wants to wade through 5000 lines to find your syntax errors!
    - Often you discover your own mistake whilst writing an SSCCE.
    - Often you solve your own problem whilst preparing the SSCCE.
    - Solving your own problem yields a sense of accomplishment, which makes you smarter ;-)
h5. Formatting Matters
* Post your code between a pair of &#123;code} tags
    - That is: &#123;code} ... your code goes here ... &#123;code}
    - This makes your code easier to read by preserving whitespace and highlighting java syntax.
    - Copy&paste your source code directly from your editor. The forum editor basically sucks.
    - The forums tabwidth is 8, as per [the java coding conventions|http://java.sun.com/docs/codeconv/].
      - Indents will go jagged if your tabwidth!=8 and you've mixed tabs and spaces.
      - Indentation is essential to following program code.
      - Long lines (say > 132 chars) should be wrapped.
* Post your error messages between a pair of &#123;code} tags:
    - That is: &#123;code} ... errors here ... &#123;code}
    - OR: &#91;pre]&#123;noformat} ... errors here ... &#123;noformat}&#91;/pre]
    - To make it easier for us to find, Mark the erroneous line(s) in your source-code. For example:
        System.out.println("Your momma!); // <<<< ERROR 1
    - Note that error messages are rendered basically useless if the code has been
      modified AT ALL since the error message was produced.
    - Here's [How to read a stacktrace|http://www.0xcafefeed.com/2004/06/of-thread-dumps-and-stack-traces/].
* The forum editor has a "Preview" pane. Use it.
    - If you're new around here you'll probably find the "Rich Text" view is easier to use.
    - WARNING: Swapping from "Plain Text" view to "Rich Text" scrambles the markup!
    - To see how a posted "special effect" is done, click reply then click the quote button.
If you (the newbie) have covered these bases *you deserve, and can therefore expect, GOOD answers!*
h1. The pledge!
We the New To Java regulars do hereby pledge to refrain from flaming anybody, no matter how gumbyish the question, if the OP has demonstrably tried to cover these bases. The rest are fair game.