parse comma delimited text string

[electrixnow]

in MS VC++ Express I need to know how to get from one comma delimited
text string to many strings.

from this:

main_string = "onE,Two,Th ree , fouR,five, six "

to these:

string1 = "one"
string2 = "two"
string3 = "three"
string4 = "four"
string5 = "five"
string6 = "six"

the white space needs to be removed and the case needs to be all upper
or lower.
The result needs to be strings and not pointers or addresses in memory
so I can test:

string test = "three";

if (three == "three")

some getlines will only have two strings some may have up to 10
Please help with examples, you input with exact syntax is greatly
appreciated

I have been struggling with not using pointers but every time I end up
using them.

Thanks in advance

[Dietmar Kuehl]

Alf P. Steinbach wrote:

result[i] = static_cast<cha r>( std::toupper( s[i] ) );

The above line shall read

result[i] = std::toupper( static_cast<uns igned char>(s[i]));

While the compiler automatically takes care of the conversion from
'char' to 'int', it could produce negative values on systems where
'char' is a signed type without the explicit conversion to 'unsigned
char'. However, 'std::toupper(i nt)' only accepts positive values
making it necessary to convert the 'char' to an 'unsigned char'
first.
--
<mailto:di***** ******@yahoo.co m> <http://www.dietmar-kuehl.de/>
<http://www.eai-systems.com> - Efficient Artificial Intelligence

[Daniel T.]

In article <44************ @individual.net >,
Dietmar Kuehl <di***********@ yahoo.com> wrote:

Daniel T. wrote:

int (*lower)(int) = &tolower;
transform( str.begin(), str.end(), str.begin(), lower );

Note that this does *NOT* work! The argument to 'std::tolower() '
has to be an *unsigned* value. However, on platforms where 'char'
is signed, the argument could expand to a negative value! In
portable code, the only valid call to 'std::tolower(i nt)' with a
'char' looks like this:

std::tolower(st atic_cast<unsig ned char>(c));

The only possible variation is how the 'char' is first cast to
an 'unsigned char'.

That is only necessary if one is using an extended character set. For
all ASCII characters, "tolower( c )" will work just fine. In order to
write portable code, one must not use an extended character set, making
the cast will not magically make it portable.

--
Magic depends on tradition and belief. It does not welcome observation,
nor does it profit by experiment. On the other hand, science is based
on experience; it is open to correction by observation and experiment.

[Daniel T.]

In article <44************ @individual.net >,
Dietmar Kuehl <di***********@ yahoo.com> wrote:

Injecting existing filtering stream buffers into the processing is
pretty straight forward. Of course, writing them is not necessarily
so but it is not that hard either. The real advantage I see in the
filtering stream buffer over your code is that it encapsulates the
complete solution, especially if it is also equipped with a simple
input stream which automatically maintains the stream buffer.

I read up on streambuf's last night. Although, your solution does work,
I think it is inappropriate. Stream Buffers are supposed to represent
buffering strategies for different kinds of streams, not conversion
strategies.

Both of our codes encapsulated the complete solution.
--
Magic depends on tradition and belief. It does not welcome observation,
nor does it profit by experiment. On the other hand, science is based
on experience; it is open to correction by observation and experiment.

[Dietmar Kuehl]

Daniel T. wrote:

I read up on streambuf's last night.
Just out if interest: where did you read up on them?
Although, your solution does work,
I think it is inappropriate. Stream Buffers are supposed to represent
buffering strategies for different kinds of streams, not conversion
strategies.
Stream buffers are intended to represent streams of characters.
When streaming characters, it is quite common to transform them
in some way. Actually, this is the basis of UNIX' approach to
filters. My code effectively just did the moral equivalent of
"tr 'A-Z,' 'a-z '" which is, IMO, an entirely appropriate use
of streams.

In fact, even at the very basis of file streams, (i.e. in the
class template 'std::basic_fil ebuf') a heavy conversion mechanism
is employed which converts bytes read from a file into characters
used within an application or vice versa. This uses 'std::codecvt'
facets and it would be an easy typing exercise to inject the
conversion I implemented in the stream buffer into a corresponding
facet.
Both of our codes encapsulated the complete solution.

Well, I somewhat disagree with this statement but then, the
problem was trivial enough that it may not be worth to encapsulate
the solution further than you did.
--
<mailto:di***** ******@yahoo.co m> <http://www.dietmar-kuehl.de/>
<http://www.eai-systems.com> - Efficient Artificial Intelligence

[Julián Albo]

Daniel T. wrote:

That is only necessary if one is using an extended character set. For
all ASCII characters, "tolower( c )" will work just fine. In order to
write portable code, one must not use an extended character set, making
the cast will not magically make it portable.

As far as I know, standard C++ does not privilege the ascii charset in any
way, nor any other 0-127 charset.

Of course you have less problems if you know for sure that all your users
use ascii. But you will also have less users.

--
Salu2

[Alf P. Steinbach]

* Dietmar Kuehl:

Alf P. Steinbach wrote:

result[i] = static_cast<cha r>( std::toupper( s[i] ) );
The above line shall read

result[i] = std::toupper( static_cast<uns igned char>(s[i]));

Thanks for that correction, it was a screw-up.

While the compiler automatically takes care of the conversion from
'char' to 'int', it could produce negative values on systems where
'char' is a signed type without the explicit conversion to 'unsigned
char'. However, 'std::toupper(i nt)' only accepts positive values
And EOF. ;-)

making it necessary to convert the 'char' to an 'unsigned char'
first.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?