Outputting the size of an array

[tigrfire]

I need the following code to return a string of character stored in
array and also return the size of the array. I want to do it without
using pointers and so far have the character storing working fine, it's
just that I can't really think of a way to return the number of
characters in the array. Anyone help me out?

int inputPhrase()
{
char msg[characters], ch;
int i = 0;
int n = 5;

while ((ch = getchar()) != '\n')
{
msg[i++] = ch;
}

msg[i] = '\0'; /* prevents garbage from being place at end of array
output */

i = 0;

while (msg[i] != '\0')
{
printf("%c", msg[i++]);
}

return n;
}

int main()
{
inputPhrase();

int size = inputPhrase();
printf("%d\n", size);

return 0;
}

[pete]

tigrfire wrote:

I've modified my code as you mentioned and also made some syntatical
changes that Jack recommended. I'm now trying to do a number of things
with my code:
1. I'm writing a function called cleanUpPhrase that removes
punctuation and whitespace. I'm going to try and accomplish this using
tolower() and isAlpha() from the ctype library I've included. I'm just
a little confused on how I can pass the string of chars from my
inputPhrase function into my cleanUpPhrase function.
2. On another note, I'm also trying to modify my inputPhrase
function so that if the user-inputted
string of chars is longer than 30
chars long, it will truncate the message and only output the first 30
chars. In my main function I used an if loop to truncate the size, but
nothing I've tried in my inputPhrase function to truncate the actual
returned message output is working.

Here's the code:

/* BEGIN new.c */

#include <stdio.h>
#include <ctype.h>

#define MAX_CHARS 30

size_t inputPhrase(cha r *msg, size_t max);

int main(void)
{
char msg[MAX_CHARS + 1];
size_t size;

size = inputPhrase(msg , sizeof msg - 1);
printf("\n%u\n" , (unsigned)size) ;
puts(msg);
return 0;
}

size_t inputPhrase(cha r *msg, size_t max)
{
size_t i;
int ch;

ch = getchar();
for (i = 0; max > i && ch != '\n' && ch != EOF; ++i) {
msg[i] = (char)ch;
ch = getchar();
}
msg[i] = '\0';
return i;
}

void cleanUpPhrase()
{

}

/* END new.c */
--
pete

[Mark McIntyre]

On 14 Nov 2005 18:34:00 -0800, in comp.lang.c , "tigrfire"
<bb******@gmail .com> wrote:

Outside the function I defined characters as:
#define characters 30

(and other contextless remarks)

--
Please quote enough of the previous message for context. To do so from
Google, click "show options" and use the Reply shown in the expanded
header.

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[pete]

tigrfire wrote:

I've modified my code as you mentioned and also made some syntatical
changes that Jack recommended. I'm now trying to do a number of things
with my code:
1. I'm writing a function called cleanUpPhrase that removes
punctuation and whitespace. I'm going to try and accomplish this using
tolower() and isAlpha() from the ctype library I've included.

There's also ispunct() and isspace() to consider.

--
pete

[Kenny McCormack]

In article <ec************ *************** *****@4ax.com>,
Mark McIntyre <ma**********@s pamcop.net> wrote:

On 14 Nov 2005 18:34:00 -0800, in comp.lang.c , "tigrfire"
<bb******@gmai l.com> wrote:

Outside the function I defined characters as:
#define characters 30

(and other contextless remarks)

--
Please quote enough of the previous message for context. To do so from
Google, click "show options" and use the Reply shown in the expanded
header.

You (and others, such as Keith) are wasting your breath. They'll never get
it. And I'll tell you why.

Imagine that there's a mouse - and the mouse is the Usenet. You and I can
see that it is a mouse and we behave accordingly. But now there is a class
of users (we'll call them "googlers") that are wearing these funny weird
glasses that make them see not a mouse, but an elephant. Seeing an
elephant (i.e., the Usenet as a web page), they also behave accordingly.
And no amount of verbiage from us is going to convince them that it's not
an elephant - that it is only a mouse.

To make this more clear, to a googler, it doesn't make any sense to "quote"
(whatever the heck that is...), in fact, to do so would be absurd, when all
the rest of the articles in the thread are right there in front of their
faces (just as clear as the trunk on that mouse, er, elephant). And no
amount of verbiage from us is going to convince them not to believe what
they see. The point is you can *never* convince someone that what they see
isn't reality. The only way you can address the problem is to help them
fix their eyesight (or help them remove their funny glasses).

Or, just let it go...

[Keith Thompson]

ga*****@yin.int eraccess.com (Kenny McCormack) writes:

In article <ec************ *************** *****@4ax.com>,
Mark McIntyre <ma**********@s pamcop.net> wrote:

On 14 Nov 2005 18:34:00 -0800, in comp.lang.c , "tigrfire"
<bb******@gma il.com> wrote:

Outside the function I defined characters as:
#define characters 30

(and other contextless remarks)

--
Please quote enough of the previous message for context. To do so from
Google, click "show options" and use the Reply shown in the expanded
header.

You (and others, such as Keith) are wasting your breath. They'll never get
it. And I'll tell you why.

You've told us why several times before. We've explained why you're
wrong (briefly, many of them *do* get it). Save your own breath.

--
Keith Thompson (The_Other_Keit h) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[Mark McIntyre]

On Wed, 16 Nov 2005 21:15:55 GMT, in comp.lang.c , Keith Thompson
<ks***@mib.or g> wrote:

ga*****@yin.in teraccess.com (Kenny McCormack) writes:
(the usual nonsense)
You've told us why several times before. We've explained why you're
wrong (briefly, many of them *do* get it). Save your own breath.

I don't see why you don't killfile the idiot. He rarely says anything
worth listening to, and is erroneous insufficiently often to endure
just so you can correct him.
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt >

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Mark McIntyre]

On Wed, 16 Nov 2005 21:15:55 GMT, in comp.lang.c , Kenny McCormack
wrote:

You (and others, such as Keith) are wasting your breath.

I dont use my breath to power my computer. I don't emit that sort of
quantity of hot air....

(sorry, the threading may get hosed on this, Kenny's in my killfile so
I had to reply to Keith and update the attrib line).
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt >

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Kenny McCormack]

In article <ln************ @nuthaus.mib.or g>,
Keith Thompson <ks***@mib.or g> wrote:
....

You've told us why several times before. We've explained why you're
wrong (briefly, many of them *do* get it). Save your own breath.

Au contraire. 'tis you that is wrong.

And that is why I must keep posting. To set the record straight each time.

[John]

Kenny McCormack wrote:

Au contraire. 'tis you that is wrong.

And that is why I must keep posting. To set the record straight each time.

Actually, people get it as long as there's someone to correct them
often. Google made it
easier for people to get on nntp groups but many, even people who posted
before using
an Usenet client and switched to Google groups don't realize that the
Reply link doesn't
work properly, and that it doesn't hide but it totally annihilates the
original
message. Also, warning people about top posting is a good idea not
necessarily for the sake
of the guys who post but for the people who bother to read. People
coming to a newsgroup
looking for an answer to a question should be aware that if someone
bothers to read
they should also use common sense when replying.

This discussion will degenerate into a children's fight... someone wants
to have the last word
even if he's not right. If you have the will to post to fight something
that makes no sense, why not
So why not let people warn others if they are willing to do that?
I hope I won the war and have the last post on this :-).

[haroon]

>many, even people who posted

before using
an Usenet client and switched to Google groups don't realize that the
Reply link doesn't
work properly, and that it doesn't hide but it totally annihilates the
original message.
just for sake of information, the reply link at bottom is quick reply
don't use it. instead near the name of poster, on top of message, click
options, then reply...
Also, warning people about top posting is a good idea not
necessarily for the sake of the guys who post but for the people who bother to read.
That's really a good idea...
People coming to a newsgroup
looking for an answer to a question should be aware that if someone
bothers to read
they should also use common sense when replying.
alas! it's not that common :P.
This discussion will degenerate into a children's fight... someone wants
to have the last word even if he's not right.
:D
If you have the will to post to fight something that makes no sense, why not
So why not let people warn others if they are willing to do that?
I hope I won the war and have the last post on this :-).

let's see.