>>>>And guess what - the society was like that since forever. I think we're actually smarter, as a civilization, than we were a generation or two ago. Okay, maybe not... I've seen things solved long ago becoming a problem again. But we still go on, live and... yup, vent our frustration at times :).
>>>
>>>Not by allowing anti-vaxxers and flat-earthers and those whose only complaint against mdot is they don't like how it looks and want to do nothing more than annoy me. Check message 01680935,
>>
>>My opinion on mdot is that it rarely matters, it's useful only as a method to invoke intellisense in the command window, the trouble that may be caused by not using it is easy avoid and yep it looks ugly. Where do I pay my excommunication fees?
>
>It matters to me because of all the crappy coders I've encountered. Do not give anyone the right to say my evidence is ill advised.
>
>In this very app I'm struggling with now, they do this...
>
>select alias
>scatter name alias.
>m.alias.property = something.
>
>They did not know anything about row or table buffering. I am pushing for better results than just stupidity. I don't want to have to use mdot, but there is no alternative. I cannot rewrite the entire system to cater to Walter's preference.

Mike, If you really read my messages, you'd know that i've recognized there are situations mdot is a reasonable solution, several times. You just read over it and strawman me over a position I do not hold.

Even when we started argueing, long, long, long ago, I've stated numerous times that avoiding the conflict between names of fields and variables are best solved by using different naming conventions, but there are situations where this is beyond your control, like when inheriting a database or a large project.

And as for your claim of 100% safety using mdot. That simply does not exists. You have posted a lot of code that isn't and I yet have to come accross code (of any significant length) that is.

So, my advice to anyone is:
1. Avoid fieldname - variable conflicts by using different naming conventions
2. When that is not possible (for whatever reason), mdot is a reasonable way to avoid it, but still a significant risk because forgetting one mdot occurence might result in a bug that is very difficult to spot.

So again, stop the strawmanning.