Re: [Ummon-devel] Reduced size

[Miroslav R. <mir...@in...>]

> 1) .old files...i had em saved before, but I find no reason to save them
> now, if we are just formatting the code for release and use.  But, if you
> want to delete all those files yourself...I won't delete them.
The reason to do that is that user might not trust the program
not to eat some part of its code. That might be some flag option (to keep or
not to keep old files).

> 2) Subs, Ok, should this be a standard feature?  Or a param?
Param :)

> 2) Object oriented code?  Don't make me shoot you like the Israeli who
wrote
> Astyle.  This is a good place for standard C.
> 3)  ini file....um, is this going to be windows only?  If not, i don't
feel
> like writing extra code for nothing.
> I am not making a VC++ Project for this, I am just writing in C.  You can
do
> whatever you want this with, vc++ gives me trouble.

OK, do what you feel best, but in my opinion ;) program must have code
flexible enough to easily add new features (I like to see code done in
layers
where each new layer - class inheritance adds another functionality on top
of previous one).
I am imagining the code to be able to:
- convert to/from unix format (CR/LF<->LF)
- eat trailing whitespace (I hope you done that, havent tested)
- support for beautifier styles (see astyle documentation) - far future :0)

Regarding ini file it might be good to use it since you would type bunch of
params each time on command line (if not using script).
One tip: Ummon project has portable ini file class (uses STL library), it
also has file enumeration
code. This is good chance to see how it works / debug it for rest of us.

> 4) Keeps adding, and the bad tabbing....i need the file you tested that
on.
Test file I used is OutlookView.cpp from WinUmmon (take a notice
on those message map entries after formatting)