revolution,

Use it as you wish and reload with lea ebp, [esp+X] when you need to access locals/parameters again.

Sure, but then you get the "what is esp pointing to?" problem again. If you are playing nicely with the macros then you won't have used push/pop and you will always remember to reload ebp before using invoke/ccall/cinvoke/stdcall with local parameters. And what if you still want to use the value in ebp for something? You have to save it somewhere, which brings us back to the "what is esp pointing to?" problem.

revolution,

That's the problem: if you know where esp points, you can use it for addressing (and spend extra byte for each), or maintain ebp and forget it altogether.

Valid stack frame is useful for unwinding too (though it's rarely used in assembly).

Yes, there are many disadvantages. This is why I made it an opt-in parameter in my macros. Only when you knew it would be beneficial and that potential traps were understood then one could use the ESP based frame. However the OP of this thread wanted to completely eliminate EBP frames. I tried to warn that this may not be a good idea. One has to consider all the potential problems, and decide whether or not it is good, at the granularity of the individual function, not on the whole program.

I'm at least going to try to keep ebp pointing to my "data segment" as much as I can, see if it is profitable. Would have been nice to be able to use es:[] or something in Windows.

Cool trick!

I would use this for better clarity though...

Or even this way...
I just think hex should be used when appropriate
and the same goes for decimal or binary or whatever.
Just for clarity, but to each his own...
But anyway, nice work, i like it!