How many lines is too many lines ?

[440bx]

You send others to do lots of works, dismiss it and ask them to do even more work. Wich you will disregard again.

I expect those who make claims to put the necessary work to establish a foundation for those claims.  That's how it's done.

What everyone here has produced is simply unsupported claims. 

ZydisInfoC is there for you or anyone else to _demonstrate_ their claims but, instead  you whine about the fact that demonstrating your claims takes work.  Well... guess what ?... yes, demonstrating a claim takes work, imagine that!.

All you people have to do is restructure code I provided. If you people are so right about creating jigsaw puzzles then it should not be that much effort to simply create the chunks you are so fond of to "improve" the code.  IOW, stop the empty claims and all the whining, provide a foundation by showing you can produce something that is less complex while still being _fully_ functionally equivalent.

Yes, that's too much to ask... it takes work... we can't have that... can we ?

The problem is this:  your jigsaw puzzle will require jumping to who knows how many chunks of code thereby breaking the linearity of the code.  In addition to that, it will almost certainly require passing parameters, something which is not required by the current code and, will be harder to test but, no doubt at all, that after it is _obvious_ that your code is significantly inferior you people will still have the gall to claim it's better.


Bottom line is this: I put my code on the line to demonstrate my claims.  You people don't.  You make baseless claims and since you cannot support your claims, you whine!.
 
ETA:  added the above "summary".

[Khrys]

Code: Pascal  [Select][+][-]

1. {$if defined(BREAK_ON_ADDRESS32_ADJUSTMENT) and defined(CONSOLE)}
2.   if IsDebuggerPresent() then
3.   begin
4.     DebugBreak();
5.   end;
6. {$endif}

The above snippet is repeated no less than 23 times in  AnalyzePe32.inc - I guess the markings on your C and V keys have long since disappeared if this is how you like to program.

I want opinions that are well founded, not just empty claims, much less a bunch of pathetic dribble.

Go find a mirror right now and say that again, maybe some of it will stick 

[440bx]

Code: Pascal  [Select][+][-]

1. {$if defined(BREAK_ON_ADDRESS32_ADJUSTMENT) and defined(CONSOLE)}
2.   if IsDebuggerPresent() then
3.   begin
4.     DebugBreak();
5.   end;
6. {$endif}

The above snippet is repeated no less than 23 times in  AnalyzePe32.inc

I didn't count the number of times, thank you for counting them for me. 

What I find interesting is that implied in your statement is that no error checking should be done... is that what you're saying ? because if error checking should be done then 23 times or 230 times or 2300 times is immaterial, errors are checked whenever necessary.

- I guess the markings on your C and V keys have long since disappeared if this is how you like to program.

No, my editor (ME) allows me to put line sequences in separate buffers and paste them as necessary and it does not use the ctrl-C and V keys to carry out the copy/paste operation.  It's single key instead, much easier and quicker.

Go find a mirror right now and say that again, maybe some of it will stick 

Maybe you and the others who have posted in this thread should take your suggestion and go to a mirror and ask "who is the _only_ person who has put code on the line to support his claims" ?... guess what ?... it is not going to say you're the one who put code on the line... but who knows, it might say you're the prettiest programmer... (I would have no basis to differ...)   LOL.

Your post, like the other contrarian posts in this thread, was not enlightening but, at least, it was entertaining. Thank you for that.