linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Satchell <list@fluent2.pyramid.net>
To: Nick Jennings <nkj@namodn.com>, linux-c-programming@vger.kernel.org
Subject: Re: using 'int char' with #define's variables.
Date: Sun, 01 Sep 2002 18:16:14 -0700	[thread overview]
Message-ID: <5.1.0.14.0.20020901181431.00aa0b80@fluent2.pyramid.net> (raw)
In-Reply-To: <20020901153529.A16903@namodn.com>

At 03:35 PM 9/1/02 -0700, Nick Jennings wrote:
>char * strrchr( char * str, int ch );
>
>   It takes a character as an int in that second param.
>
>   I am having trouble using it with a #define's VAR.
>
>---
>#define DIRMARK "/"
>
>...
>
>char * filename = strrchr(path, DIRMARK);

Your #define is of type array of char, not a plain chiar. If you were to 
define it as

#define DIRMARK '/'

it would work better.

(note single-quote instead of double-quote)


      parent reply	other threads:[~2002-09-02  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01 22:35 using 'int char' with #define's variables Nick Jennings
2002-09-01 22:28 ` Adam Kropelin
2002-09-02  1:16 ` Stephen Satchell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.0.20020901181431.00aa0b80@fluent2.pyramid.net \
    --to=list@fluent2.pyramid.net \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=nkj@namodn.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).