Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #85258

Re: Two versions of K&R exercise 3-5: one doesn't print the string

Show all headers | View raw

Barry Schwarz <schwarzb@dqel.com> writes:
> On Tue, 29 Mar 2016 09:00:25 -0700, Keith Thompson <kst-u@mib.org>
> wrote:
>>Barry Schwarz <schwarzb@dqel.com> writes:
>>> On Mon, 28 Mar 2016 11:49:16 -0700 (PDT), Alla _
>>> <modelling.data@gmail.com> wrote:
>>[...]
>>>>    if (argc < 3)
>>>>    {
>>>>        printf("Usage: ./program, number, base\n");
>>>
>>> When using printf to print string like this (either literal, array, or
>>> pointer), there is a benefit to coding it as
>>>      printf("%s", your string parameter here);
>>> This will eliminate any problems if your string should happen to
>>> contain any '%'.  As you have written it, the '%' would be interpreted
>>> as the start of a format conversion.
>>
>>I'd probably put the newline in the format string:
>>
>>    printf("%s\n", "Usage: ./program, number, base");
>>
>>Another option (I prefer this one):
>>
>>    puts("Usage: ./program, number, base");
>
> puts() forces a newline.  OK for the example but not so much for a
> prompt to enter a value.

The argument to the printf() had a newline in it.  That's the only
reason I suggested replacing it with puts().  If you want to print a
string literal without a newline, you'd have to use
    fputs("some string", stdout);
which I still slightly prefer to
    printf("%s", "some string");
but it's a closer call.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Two versions of K&R exercise 3-5: one doesn't print the string Alla _ <modelling.data@gmail.com> - 2016-03-28 11:49 -0700
  Re: Two versions of K&R exercise 3-5: one doesn't print the string Paul N <gw7rib@aol.com> - 2016-03-28 13:42 -0700
    Re: Two versions of K&R exercise 3-5: one doesn't print the string Alla _ <modelling.data@gmail.com> - 2016-03-30 04:01 -0700
  Re: Two versions of K&R exercise 3-5: one doesn't print the string Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-28 22:29 +0100
  Re: Two versions of K&R exercise 3-5: one doesn't print the string Barry Schwarz <schwarzb@dqel.com> - 2016-03-28 22:05 -0700
    Re: Two versions of K&R exercise 3-5: one doesn't print the string Jerry Stuckle <jstucklex@attglobal.net> - 2016-03-29 08:49 -0400
    Re: Two versions of K&R exercise 3-5: one doesn't print the string Keith Thompson <kst-u@mib.org> - 2016-03-29 09:00 -0700
      Re: Two versions of K&R exercise 3-5: one doesn't print the string Barry Schwarz <schwarzb@dqel.com> - 2016-03-29 10:42 -0700
        Re: Two versions of K&R exercise 3-5: one doesn't print the string Keith Thompson <kst-u@mib.org> - 2016-03-29 12:12 -0700
  Re: Two versions of K&R exercise 3-5: one doesn't print the string programming109@gmail.com - 2016-04-11 08:29 -0700
    Re: Two versions of K&R exercise 3-5: one doesn't print the string programming109@gmail.com - 2016-04-11 08:35 -0700
    Re: Two versions of K&R exercise 3-5: one doesn't print the string Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-04-11 19:59 +0100
      Re: Two versions of K&R exercise 3-5: one doesn't print the string programming109@gmail.com - 2016-04-11 22:41 -0700
        Re: Two versions of K&R exercise 3-5: one doesn't print the string luser droog <luser.droog@gmail.com> - 2016-04-11 23:18 -0700
        Re: Two versions of K&R exercise 3-5: one doesn't print the string Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-04-12 11:02 +0100
    Re: Two versions of K&R exercise 3-5: one doesn't print the string Keith Thompson <kst-u@mib.org> - 2016-04-12 11:26 -0700

csiph-web