# "\_" and "\*" being synonymous is redundant and confusing

**URL:** <https://talk.commonmark.org/t/--and-being-synonymous-is-redundant-and-confusing/282>\
**Category:** Spec\
**Created:** [September 4, 2014, 11:43am UTC](https://talk.commonmark.org/t/--and-being-synonymous-is-redundant-and-confusing/282 "2014-09-04T11:43:02Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jgm](https://talk.commonmark.org/user_avatar/talk.commonmark.org/jgm/32/1360_2.png) [@jgm](https://talk.commonmark.org/u/jgm)\
**Post date:** [September 4, 2014, 5:30pm UTC](https://talk.commonmark.org/t/--and-being-synonymous-is-redundant-and-confusing/282/5 "2014-09-04T17:30:30Z")

</div>

Backwards compatibility was a major goal. Of course, implementations  
vary enough that it’s impossible to avoid all breakage. But we want to  
minimize it.

---

_[View the full topic](https://talk.commonmark.org/t/--and-being-synonymous-is-redundant-and-confusing/282)._
