public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Carter <john.carter@tait.co.nz>
To: David <decibel8@charter.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Stdprn in GCC
Date: Tue, 22 Oct 2002 15:06:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0210231102140.11006-100000@parore> (raw)
In-Reply-To: <3DB5C572.6010008@charter.net>

On Tue, 22 Oct 2002, David wrote:

>     Starting to learn C Programming all over again in Linux this time.
> 
> The problem is that most books are for Windows/Dos also.
> 
> 'stdprn'   is not contained in stdio.h in GCC.

If you want it to come out (directly) /dev/lp0 (the line printer port) 
just open that and fire away.

Either that stuff it in a file and invoke "lpr fileName" at a later stage.

You can also pipe either stdout to "lpr" or fork and pipe to lpr.

A good reference source if the Linux Documentation Project (ask google) 
and in particular the Linux Programmers Guide.

-- 


John Carter                             Phone : (64)(3) 358 6639
Tait Electronics                        Fax   : (64)(3) 359 4632
PO Box 1645 Christchurch                Email : john.carter@tait.co.nz
New Zealand

Good Ideas:
Ruby                 - http://www.ruby-lang-org - The best of perl,python,scheme without the pain.
Valgrind             - http://developer.kde.org/~sewardj/ - memory debugger for x86-GNU/Linux
Free your books      - http://www.bookcrossing.com

  reply	other threads:[~2002-10-22 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 14:41 David
2002-10-22 15:06 ` John Carter [this message]
2002-10-22 15:08 ` bjorn rohde jensen
2002-10-22 16:13 David
2002-10-23 13:35 ` John Carter

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=Pine.LNX.4.44.0210231102140.11006-100000@parore \
    --to=john.carter@tait.co.nz \
    --cc=decibel8@charter.net \
    --cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).