linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rhys <rhiannon@miranda.inetsolve.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: limited range of data error
Date: Mon, 20 Mar 100 17:28:06 -0500 (EST)	[thread overview]
Message-ID: <200003202228.RAA22962@miranda.inetsolve.com> (raw)


When i try to compile i get these errors:

act_comm.c: In function 'send_ascii_title':
act_comm.c:2234: warning: comparison is always true due to
limited range of data type

This is from a redhat system. I think there are
problems with me missing the files related to
fgetc() and fopen(). Anyone have any ideas for
how to get this to work?

Relevent code is:

send_ascii_title( CHAR_DATA *ch )
{
   FILE *rpfile;
   int num=0;
   char BUFF[MAX_STRING_LENGTH];

   if ((rpfile = fopen(ASCTITTLE_FILE, "r")) !=NULL) {
     while (( BUFF[num]=fgetc(rpfile)) != OEF) // Line 2234
        num++;
     fclose(rpfile);
   BUFF[num] = 0;
   write_to_buffer( ch->desc, BUFF, num );
   }
}

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-03-20 22:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 22:28 Rhys [this message]
2000-03-20 23:12 ` limited range of data error Gabriel Paubert
2000-03-21  1:54 ` David A. Gatwood
2000-03-21  2:22   ` Gabriel Paubert
2000-03-21 19:48 ` stty crtscts < /dev/ttyS1 DeRobertis
2000-03-22 16:05   ` Matt Haffner
     [not found]     ` <l03130300b4ff357b23e8@[216.164.129.33]>
2000-03-23 11:17       ` stty crtscts < /dev/ttyS1 [603ev] ce
2000-03-25  6:06         ` DeRobertis
2000-03-23 13:34     ` communicate with peripherics ? Franck Chionna
     [not found]   ` <l03130304b50c8e1b783f@[216.164.131.253]>
2000-04-08  0:35     ` stty crtscts < /dev/ttyS1 Giuliano Pochini
2000-04-08  4:05       ` DeRobertis
2000-04-08 17:08         ` Greg Noel
2000-04-09  0:02           ` Giuliano Pochini
2000-04-09 17:42           ` DeRobertis
2000-04-09  0:20         ` Giuliano Pochini

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=200003202228.RAA22962@miranda.inetsolve.com \
    --to=rhiannon@miranda.inetsolve.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).