Suggested coding style

[alex23]

On Sep 29, 10:23 pm, rantingrick <rantingr... at gmail.com> wrote:
> What is so bad about breaking code in obscure places?

Try coding in PHP across minor release versions and see how you feel
about deprecating core functions on a whim.

> We changed print
> to a function which broke just about every piece of code every written
> in this language.

In a well declared _break_ with backwards compatibility. Not on a whim
between minor releases.

> (BTW, print should ALWAYS have been a function!)

Unfortunately, not everyone is as infallible as you. Or as
intractable. Coding styles change over time: this is a concept known
as "progress", although it's not as obvious in monocultures, so you
may not have heard of it.

> What is so bad then about breaking some very obscure code?

Because while you say "some very obscure code", what you really mean
is "code that isn't mine".

> GvR should be texting me every night in hopes that some of my API genius will rub
> off on him.

Are you off your medication again?

> I believe GvR had a "mid-dev-crisis"[...]

You seem to believe a lot of absolute garbage. As you have no access
to the inner states of _any_ of the people you regularly condemn here
with your hypocritical attacks, I've no idea why you consider yourself
to be an expert on their desires and opinions.