×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu, Nov 12, 2015 at 9:43 AM, Vernon Hamberg
<vhamberg@xxxxxxxxxxxxxxx> wrote:
I would think no editor should ever have behavior that prevents using what
is otherwise valid code. And I am sure the RDi team feels the same way.
Actually, it is a pretty common thing for editors to not know every
intricacy of a programming language. For many if not most languages,
100% correctness is a significant burden (because the editor would
essentially need to duplicate or reimplement logic from the compiler,
or farm out syntax checking to the compiler).
When someone says they are "modifying their code" to get around editor
restrictions, they usually mean benign things like finagling comments
so that highlighting or bracket-matching is more useful, or
artificially limiting line lengths to stay within screen or editor
capabilities, rather than language specification.
You did bring up the situation where the language has changed and the
editor has not yet caught up, but I think there will always be some
corner cases that it's understandable and acceptable for an editor not
to implement, even if that editor is billed as fully up to date.
John Y.
midrange.com
