472,122 Members | 1,421 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,122 software developers and data experts.

Please help with File IO

Hello,

I have a text file I'm attempting to parse. There are about 50 fixed width
fields in each line / row. For example (shortened for brevity):

W1234Somebody East 101110001111010101
E1235Someone Else West 010111001001010101

I'm having problems pulling these fields into structures, in order to be
able to access each individually. I am currently opening as a sequential
file. Is there a better way?

My structure looks something like:

struct data{
char area[1];
char empNumber[4];
char name[16]
char region[5];
char options[20];
}

int index = 0;
data user[100];

I would like to read the entire file into memory. Please tell me if I'm
going about this the wrong way. So far after reading the file in, I'm
unable to access any individual items (ie. user[index].area) Also should
I stick with a sequential file, or should I consider binary access (seems
like it may be easier to address individual elements)?

(I don't want to include too many details here, but will be happy to provide
whatever is needed).

Thank you in advance,
Brian
Jul 22 '05 #1
2 1549
"Brian" <bk****@hotmail.com> wrote in message news:3d**************************@posting.google.c om...
Hello,

I have a text file I'm attempting to parse. There are about 50 fixed width
fields in each line / row. For example (shortened for brevity):

W1234Somebody East 101110001111010101
E1235Someone Else West 010111001001010101

I'm having problems pulling these fields into structures, in order to be
able to access each individually. I am currently opening as a sequential
file. Is there a better way?

My structure looks something like:

struct data{
char area[1];
char empNumber[4];
char name[16]
char region[5];
char options[20];
}

int index = 0;
data user[100];

I would like to read the entire file into memory. Please tell me if I'm
going about this the wrong way.
The information you provide does not permit such a conclusion.
Diagnosing "The wrong way" would have to be based on your
requirements, unstated so far. Your approach is going to present
difficulties if the format changes, but I presume you know that.
So far after reading the file in, I'm
unable to access any individual items (ie. user[index].area)
I cannot translate "I'm unable to access" into a familiar fact.
Do you mean "I can access individual fields but their values
differ from what I expected."? Or is it something else? If
the former: What did you get? What did you expect? And
why did you expect it? If the latter, please elaborate.
Also should
I stick with a sequential file, or should I consider binary access (seems
like it may be easier to address individual elements)?
I have not heard of "sequential file" in connection with the
standard C or C++ libraries. If you are distinguishing that
from files opened in binary mode, then, from the fact that
you claim to be dealing with a "text file", it is clear that you
do not want binary mode. The "not binary" mode is often
known as "text mode". Files are considered a sequential
series of bytes whether binary or not.
(I don't want to include too many details here, but will be happy to provide
whatever is needed).
It would probably help to see the call you use to read in
the file, together with enough data to know what values
the call parameters have.

You have given few clues as to how records are separated
in your input file. Are line-ends used for that? If so, your
attempt to blast in a whole series of records fails to account
for the space taken by the record separators. If not, your
example is misleading.
Thank you in advance, Good luck.
Brian

--
--Larry Brasfield
email: do***********************@hotmail.com
Above views may belong only to me.
Jul 22 '05 #2
Hi Larry,

I just posted my code and a sample of the data as a follow-up to my
other post: "Best way to access this File?". I do apologize for the
post - I realize I didn't do a good job in posing the question.

Thanks!
Brian

"Larry Brasfield" <do***********************@hotmail.com> wrote in message news:<BM***************@news.uswest.net>...
"Brian" <bk****@hotmail.com> wrote in message news:3d**************************@posting.google.c om...
Hello,

I have a text file I'm attempting to parse. There are about 50 fixed width
fields in each line / row. For example (shortened for brevity):

W1234Somebody East 101110001111010101
E1235Someone Else West 010111001001010101

I'm having problems pulling these fields into structures, in order to be
able to access each individually. I am currently opening as a sequential
file. Is there a better way?

My structure looks something like:

struct data{
char area[1];
char empNumber[4];
char name[16]
char region[5];
char options[20];
}

int index = 0;
data user[100];

I would like to read the entire file into memory. Please tell me if I'm
going about this the wrong way.


The information you provide does not permit such a conclusion.
Diagnosing "The wrong way" would have to be based on your
requirements, unstated so far. Your approach is going to present
difficulties if the format changes, but I presume you know that.
So far after reading the file in, I'm
unable to access any individual items (ie. user[index].area)


I cannot translate "I'm unable to access" into a familiar fact.
Do you mean "I can access individual fields but their values
differ from what I expected."? Or is it something else? If
the former: What did you get? What did you expect? And
why did you expect it? If the latter, please elaborate.
Also should
I stick with a sequential file, or should I consider binary access (seems
like it may be easier to address individual elements)?


I have not heard of "sequential file" in connection with the
standard C or C++ libraries. If you are distinguishing that
from files opened in binary mode, then, from the fact that
you claim to be dealing with a "text file", it is clear that you
do not want binary mode. The "not binary" mode is often
known as "text mode". Files are considered a sequential
series of bytes whether binary or not.
(I don't want to include too many details here, but will be happy to provide
whatever is needed).


It would probably help to see the call you use to read in
the file, together with enough data to know what values
the call parameters have.

You have given few clues as to how records are separated
in your input file. Are line-ends used for that? If so, your
attempt to blast in a whole series of records fails to account
for the space taken by the record separators. If not, your
example is misleading.
Thank you in advance,

Good luck.
Brian

Jul 22 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Dan | last post: by
3 posts views Thread by JGBNS via DotNetMonster.com | last post: by
25 posts views Thread by n3crius | last post: by
2 posts views Thread by trihanhcie | last post: by
22 posts views Thread by KitKat | last post: by
22 posts views Thread by Amali | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.