dev-cpp-users

[Big P. <big...@gm...>]

Hi,

Reid & Matt, thx for your fast answers!
I don't want to go into databases, I really don't need any features it
would offer me, but on the other hand, I'd be a bit limited since
later I might be using/saving arbitary data based on my options and
memory state (ie. different registers for different MPUs, and I know
how this could be solved with DBs, but want plain structure rather
than related things).
Reid, overloading the << operator will work I think.
I think I'll stuck with a struct anyway, and use it inside a class.
possibly I'll have duplicate entries and use them for runtime, but
convert to/from simple data formats at I/O time. I don't need, and in
fact don't want to enable users to edit these options, since changing
some of them might need converting of all other data, even
restructuring of it (and this is what this editor is designed to do,
anyway :). these are not the editor options which I'm using wxConfig
for. you're right I'm keeping an eye on portability, but at first, I
want to stay on x86 platform (but later a linux port would be fine,
bot no other systems do I plan for), and, I might be loosing
portability anyway when dumping my memory area (which I really want to
handle as-is).
just to make things clear, I'm writing an enchanced hex editor, with
abilities suitable for various MPUs. sorry if I bored the list. :))

tom

-- 
Coupe Quattro '89
Typ81 custom '84