You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- related (possibly a duplicate): Is there a correlation between the scale of the project and the strictness of the language?gnat– gnat2015-09-12 13:42:59 +00:00Commented Sep 12, 2015 at 13:42
- 2@gnat Are you saying that the answer is "use different processes and other heavyweight stuff"? I mean, that's probably not wrong, but it's also over-general to the point of not being particularly useful.senshin– senshin2015-09-12 16:43:05 +00:00Commented Sep 12, 2015 at 16:43
- 3Honestly, I don't think there is an answer to this other than "switch to a language where variables actually have scoping rules" or "use the bastard stepchild of Hungarian notation where every variable is prefixed by its file and/or method name rather than type or kind". The issue you describe is just so terrible I can't imagine a good solution.Ixrec– Ixrec2015-09-12 18:27:11 +00:00Commented Sep 12, 2015 at 18:27
- 1@DocBrown Obviously nobody's going to do greenfield development in MUMPS (dear god, at least I hope not), but if you're stuck with an enormous codebase, you've got to make do with what you've got. (Aside: porting off of MUMPS in particular is further complicated by the fact that MUMPS is also a database system - so even if you port the procedural stuff to another language, you're still going to need some amount of core logic/bindings in MUMPS anyway.)senshin– senshin2015-09-12 22:03:09 +00:00Commented Sep 12, 2015 at 22:03
- 5At least you can't accuse MUMPS of false advertising for being named after a nasty disease.Carson63000– Carson630002015-09-13 00:25:15 +00:00Commented Sep 13, 2015 at 0:25
| Show 7 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you