3 Jun 16:22
Re: Proposal to expand set of operator words
From: dmitrey <dmitrey15@...>
Subject: Re: Proposal to expand set of operator words
Newsgroups: gmane.comp.lang.fortress.general
Date: 2008-06-03 14:22:16 GMT
Subject: Re: Proposal to expand set of operator words
Newsgroups: gmane.comp.lang.fortress.general
Date: 2008-06-03 14:22:16 GMT
Jan-Willem Maessen wrote: > > On Jun 3, 2008, at 7:03 AM, Victor Luchangco wrote: > >> On May 30, 2008, at 2:41 AM, dmitrey wrote: >> >>> I would propose you another modification - to omit the rule "all >>> that is uppercase w/o digits is operator" >>> this brings problems with manual & automatic code translation to >>> fortress (because these names should be changed). >>> >>> for example I have a set of names (Python class constructors) "NLP", >>> "LP", "QP" etc (that are well-known names of optimization problems >>> classes), and using upper-case makes code more readable and >>> understandable than "nlp", "lp", etc (and, of course, much better >>> than _NLP_, NLP_ etc) >> >> Yeah, that all-caps names with two or more distinct letters cannot be >> identifiers has always bothered me a bit. Here's an idea that isn't >> fully worked out yet that I'd like to hear what people think about: > > Oddly, I've only had this problem with type names. > > There's one very real downside: I can't parse code visually. That is, > I can't quickly tell the operator names from the variable names. In essential fortress IDE it could be easily solved via different colors for variables and/or functions and/or operators. Regards, D.
RSS Feed