From: "Jim Christiansen" <christiansen_j@hotmail.com>
To: gcc-help@gcc.gnu.org
Subject: Help with #include <string.h>,,,
Date: Thu, 01 May 2003 02:05:00 -0000 [thread overview]
Message-ID: <Law11-F405LUOvfhaVL0001ac4b@hotmail.com> (raw)
Hello,
I'm a teacher that admins a 110 plus NT network who is trying to move 60 of
these boxes to Linux Thin Clients for all of our teaching. I have been
successful for all of our Business and IT classes, but have a problem
teaching
out of our C++ text from Lawernceville Press.
This book is a couple of years old and specically for MSVisual C++.My
students have been using Anjuta for their HTML work, and I was excited that
the programs from the text compiled and built in linux with anjuta. Now, I
have a problem with the #include <lvp\string.h> reference, and even if I
change it to:
#include <string.h> or
#include <string>
the code fails to compile.I'ld be grateful for any pointer on getting this
simple program running using anjuta and linux.#include <iostream.h>#include
<lvp\string.h>int main()
My thin server is based on Redhat8.0
#include <iostream.h>
#include <lvp\string.h> // or #include <string> or #include <string.h>
int main()
{
String Name = "LVPress";
cout.width(7); cout << Name << endl;
cout.width(9); cout << Name << endl;
cout.width(11); cout << Name << endl;
cout.width(13); cout << Name << endl;
cout.width(11); cout << Name << endl;
cout.width(9); cout << Name << endl;
cout.width(7); cout << Name << endl;
return(0);
}
Thanks for the help,
Jim
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
next reply other threads:[~2003-05-01 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 2:05 Jim Christiansen [this message]
2003-05-01 2:58 ` Oscar Fuentes
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=Law11-F405LUOvfhaVL0001ac4b@hotmail.com \
--to=christiansen_j@hotmail.com \
--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).