public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David McWherter <dtm@water.waterw.com>
To: "Orn E. Hansen" <oe.hansen@oehansen.pp.se>
Cc: Alexandre Oliva <oliva@dcc.unicamp.br>, egcs@cygnus.com
Subject: Re: Strings and Integers?
Date: Mon, 01 Dec 1997 05:31:00 -0000	[thread overview]
Message-ID: <Pine.NEB.3.96.971201082110.22105A-100000@water.waterw.com> (raw)
In-Reply-To: <199712011133.MAA10187@oehansen.pp.se>

Why don't you use the c_str() member of the string?  (Or has that gone
away in egcs - I do most of my work with G++ still).  It should give you
what you want, and I'm fairly certain it's a part of the standard...and I
don't think that the data() member has to be null terminated, according to
the standard, anyways...

-David

On Mon, 1 Dec 1997, Orn E. Hansen wrote:

> Alexandre Oliva writes:
>  > Orn E Hansen writes:
>  > 
>  > > I noticed that there is no implementation of String class.
>  > 
>  > String is part of libg++, that is not included in egcs.  egcs does
>  > include libstdc++, that provides a definition of class string in the
>  > header file <string>, not <string.h>, that is a C header-file.
>  > 
>  > There's no equivalent of libg++'s class Integer in the C++ standard
>  > library.
>  > 
> 
>  Since we're at it.
> 
>  I find <string> close to unusable :-)  The reason, is that it appears
> implemented as "pascal strings"... an example, running the trailing
> program will result in this display:
> 
> Enter? 4000
> Enter? 300
> Enter? 50,35
> Enter? 0
>  =>  4000,00 (4:4000sr/share/i18()
>  =>   300,00 (3:300)
>  =>    50,35 (5:50,35)
> 
>  You'll have to explicidly add '\0' to correct this, in the line...
> 
>  str = (*ptr) + '\0';
> 
>  While gnu 'String' is implemented, including the extra '\0', the
> absence of it, makes defining your own almost preferrable to using
> it.  I am assuming that this is a "normal" behaviour? as trying it
> on libg++ results in the precise same result...
> 
> 
> ----- program ----
> 
> #include <iostream.h>
> #include <string>
> #include <list.h>
> 
> extern "C" {
> 
> #include <stdlib.h>
> #include <locale.h>
> 
>            };
> 
> main()
> {
>   list<string> lstr;
>   list<string>::iterator ptr;
>   string str;
>   double v;
> 
>   setlocale(LC_ALL, "");
>   do {
>     cout << "Enter? ";
>     cout.flush();
>     cin >> str;
>     v = strtod(str.data(), NULL);
>     if (v != 0.0)
>       lstr.push_back(str);
>   } while (v != 0.0);
>   for (ptr = lstr.begin();ptr != lstr.end();ptr++) {
>     str = (*ptr);
>     v = strtod(str.data(), NULL);
>     cout.form(" => %8.2f (%d:%s)", v, str.length(), str.data()) << endl;
>   };
> }
> 

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
       David T. McWherter     dtm@waterw.com


      reply	other threads:[~1997-12-01  5:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-30  6:03 Orn E. Hansen
1997-11-30 14:29 ` Alexandre Oliva
1997-12-01  3:36   ` Orn E. Hansen
1997-12-01  5:31     ` David McWherter [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=Pine.NEB.3.96.971201082110.22105A-100000@water.waterw.com \
    --to=dtm@water.waterw.com \
    --cc=egcs@cygnus.com \
    --cc=oe.hansen@oehansen.pp.se \
    --cc=oliva@dcc.unicamp.br \
    /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).