Edit - Software Engineering Stack Exchange

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.

Thank you! Re: internals - when qualifying operations in source code, what is the smallest "unit" the qualification can apply to? Also, about reasonable implementations, is POSIX a guarantee of that for shell utils? Finally, by "opacity" (about statements in scripts) did you mean anything technical or just that it's harder than with non scripted languages - if so is there a reason for that?

user132481
– user132481

2014-05-25 19:44:35 +00:00
Commented May 25, 2014 at 19:44
1

The only rule for quantifying operations is that you have identify the steps whose execution time depends on the size of the data set and those that don't. By opacity I simply meant that you have to go extra effort to see the source code for the shell commands and utility programs in order to carry out the analyis.

user4828
– user4828

2014-05-25 20:42:02 +00:00
Commented May 25, 2014 at 20:42

Add a comment |

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

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>

formatting help »
answering help »