I approve of case-sensitivity where an initial Capital letter indicates that <i>Something</i> is Publically accessible and it really doesn&#x27;t matter what happens after that. Hence, we could have:<p><pre><code>  Newton-Raphson Runge-Kutta Fast-Fourier-Transform

  Class-ID IO-Channel MIDI-port 

  Freudian-Id Io-Channel
</code></pre>
In contrast to this, I feel it makes sense to have lowercase mean that <i>something</i> is private. Hence, no camelCase:<p><pre><code>  x y z variable longer-variable-name
</code></pre>
I&#x27;ve never been that comfortable about appending numerals to the end of identifiers to disambiguate them as I feel that this is a sign that they ideally ought to be subscripted and implemented as arrays. I much prefer hyphens to underscores but would ideally like to use individual words separated by spaces. This can only work if you have an IDE that hides all the underscores (which are incredibly ugly and serve no useful purpose in printed material these days) as you input them and outputs NBSPs instead and then uses similarly suppressed prefix sigils to style your raw input text into an output which conforms to traditional Mathematical notation. Hence, we could have:<p><pre><code>  &#x2F;foo_bar + &#x2F;bar_qux
</code></pre>
become:<p><i>foo bar</i> + <i>bar qux</i><p>similarly, the following is not a problem if you take advantage of the syntax rule that requires at least one space either side of an operator. Hence, we could have:<p><pre><code>  &#x2F;foo_bar &#x2F; &#x2F;bar-qux
</code></pre>
become:<p><i>foo bar</i> &#x2F; <i>bar-qux</i><p>i.e. the &#x2F; sign isn&#x27;t echoed when you initially type it as it is expecting a letter, but when the IDE receives whitespace it belatedly echoes it as the operator symbol as it is now sure that it isn&#x27;t a suppressed sigil.