# Code fences don't seem to deal with C comments

**URL:** https://meta.discourse.org/t/code-fences-dont-seem-to-deal-with-c-comments/33339
**Category:** Support
**Created:** [2015 年9 月 16 日 05:47 UTC](https://meta.discourse.org/t/code-fences-dont-seem-to-deal-with-c-comments/33339 "2015-09-16T05:47:35Z")
**Posts on this page:** 1
**Showing post:** 23

<div class="post-metadata">

### 作者： ![isagalaev](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/isagalaev/32/116712_2.png) [@isagalaev](https://meta.discourse.org/u/isagalaev)
#### 发布日期： [2015 年9 月 17 日 04:41 UTC](https://meta.discourse.org/t/code-fences-dont-seem-to-deal-with-c-comments/33339/23 "2015-09-17T04:41:21Z")

</div>

Hey there! The author of highlight.js here 🙂

@codinghorror is spot on: indeed this code is recognized as something else because there’s enough of interesting stuff happening within the comment. This is one of the cases where heuristics fails and that’s why we have the ability to set the language explicitly — don’t refrain from using it!

Having said that, I think it will be possible to improve our heuristics across the board so highlighting of this comment will probably be fixed as a side effect.

---

_[View the full topic](https://meta.discourse.org/t/code-fences-dont-seem-to-deal-with-c-comments/33339)._