Mail Archives: djgpp/2000/05/19/16:00:24
Hans-Bernhard Broeker wrote:
[snip]
You're correct and most of others are correct as well. Moreover, I have
almost nothing against of size_t use and use of other types.
> After all: what *is* so bad about size_t in your opinion that makes
> you try to avoid it like the plague? Using it you'ld have one nasty
> detail less to worry about.
Well, I just figured out a question that I have no answer to. Since size_t
is used to represent objects' sizes and probably some other stuff and fpos_t
is used for file positions, etc etc.
NOTE: size_t is from Borland C. I don't know which types are used for this
in DJGPP/GCC, I use size_t in this message just for _illustrative purpose_.
How do I work with all those types? For example, if file position depends on
a string length, how do I mix those size_t and fpos_t correctly? Isn't it
the same problem as int<->size_t type casting/conversion? size_t and fpos_t
may be represented by integers with different length (in bytes).
Any ideas?
--
Alexei A. Frounze
-----------------------------------------
Homepage: http://alexfru.chat.ru
Mirror: http://members.xoom.com/alexfru
- Raw text -