From: Oscar Fuentes <ofv@wanadoo.es>
To: gcc-help@gcc.gnu.org
Cc: christiansen_j@hotmail.com
Subject: Re: Help with #include <string.h>,,,
Date: Thu, 01 May 2003 02:58:00 -0000 [thread overview]
Message-ID: <issvs75u.fsf@wanadoo.es> (raw)
In-Reply-To: <Law11-F405LUOvfhaVL0001ac4b@hotmail.com>
"Jim Christiansen" <christiansen_j@hotmail.com> writes:
> 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++.
This possibly means it explains how to program MSVC++, not C++. MSVC++
v6 implements a dialect of C++. Most sources written by "MSVC++ only"
people are not compilable by true C++ compilers. g++ is much more
compliant with the ISO standard.
> 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>
Have you tried #include "lvp/string.h" ?
(Observe slash orientation)
[snip]
I don't know what 'anjuta' is, but I hope this does what you want:
// Standard C++ Libray lives on headers without the .h suffix
#include <iostream>
#include <string>
int main()
{
// Standard C++ Library names are on namespace 'std'
// We inject 'cout' and 'end' on the current namespace to save
// typing 'std::' lots of times
using std::cout;
using std::endl;
std::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);
}
--
Oscar
prev parent reply other threads:[~2003-05-01 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 2:05 Jim Christiansen
2003-05-01 2:58 ` Oscar Fuentes [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=issvs75u.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=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).