Sorry for the confusion.
The kids use input/output streams and the overloaded stream insertion
and extraction operators call the built in insertion/extraction
operators for each field of the struct which are either primitive types
or are structs themselves which have overloaded insertion/extraction
operators written for them:
istream & operator>> (istream & is, myStructType & record)
{
// use getline to read a line from the stream
// parse the line to get the data members of the struct
// then store them into the record
record.firstField = intFromParsingTheLine;
return is;
}
ostream & operator<< (ostream & os, const myStructType & aStruct)
{
os << aStruct.integerDataMember;
// blah, blah
return os;
}
I just had a thought. Could the problem be that we're using the old
i/ostream libraries? Are they not updated for the unicode encoding?
steve
On Sun, 2002-10-27 at 14:39, Gordon Messmer wrote:
> On Sat, 2002-10-26 at 21:53, Steve Strong wrote:
> > On Sat, 2002-10-26 at 23:16, Gordon Messmer wrote:
> > >
> > > > but when written out to the file, the text is corrupted.
> > >
> > > What functions are you using to write the text?
> >
> > we are using overloaded stream insertion operators.
>
> Right, but what mechanism are you using to overload the normal output
> routines?
>
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
--
Steve Strong
Computer Science Teacher
Washington High School
2205 Forest Dr. SE
Cedar Rapids, IA 52403
mailto: [EMAIL PROTECTED]
website: http://crwash.org
telephone: 319-398-2161
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
