home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!spool.mu.edu!olivea!sgigate!odin!news
- From: ib@ivan.asd.sgi.com (Ivan Bach)
- Newsgroups: comp.sys.sgi
- Subject: Re: CDAUDIO.H
- Keywords: uchar, unsigned character, cdaudio.h
- Message-ID: <1992Nov23.161714.2449@odin.corp.sgi.com>
- Date: 23 Nov 92 16:17:14 GMT
- References: <sljeggg@zuni.esd.sgi.com>
- Sender: news@odin.corp.sgi.com (Net News)
- Organization: Silicon Graphics, Inc., Mountain View, CA
- Lines: 17
- Nntp-Posting-Host: ivan.asd.sgi.com
-
- In <1992Nov21.162022.13540@discus.technion.ac.il> ori@marvin.technion.ac.il
- (Ori Degani) writes:
- > Can anyone tell me what the type unchar means?
- > It shows up in /usr/include/{cdaudio dataudio}.h
- As Dave Olson posted, 'uchar' stands for 'unsigned char.'
-
- One C compiler (cc) option I find very useful is the option -P:
-
- "Run only the C macro preprocessor and put the result for each
- source file (by suffix convention, i.e., '.c' and '.s') in a
- corresponding `.i' file. The `.i' file has no `#' lines in it."
-
- If you look at a .i file, you can see where things are defined, what was
- included in your program, and how your code was preprocessed, i.e., you can
- see the preprocessed code that is used as input to a C compiler.
-
- Ivan Bach, ib@sgi.com
-