Edit - Stack Overflow

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.

1

The first two bullet points you suggest are bad practice and I wouldn’t recommend. The only time you want to disable warnings are when you run on production. Never use @, ever. There’s always a better alternative.

Ollie Saunders
– Ollie Saunders

2011-11-26 23:34:06 +00:00
Commented Nov 26, 2011 at 23:34
@Ollie - Granted I stated that the options are available, but I didn't recommend them; I explicitly stated that the isset() option was the one to go for.

Spudley
– Spudley

2011-11-27 18:10:01 +00:00
Commented Nov 27, 2011 at 18:10

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 »

Collectives™ on Stack Overflow