# This is why I hate ASDoc

**URL:** <https://forum.kirupa.com/t/this-is-why-i-hate-asdoc/319084>\
**Category:** random\
**Created:** [February 8, 2011, 4:10pm UTC](https://forum.kirupa.com/t/this-is-why-i-hate-asdoc/319084 "2011-02-08T16:10:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![IQAndreas](https://avatars.discourse-cdn.com/v4/letter/i/f08c70/32.png) [@IQAndreas](https://forum.kirupa.com/u/IQAndreas)\
**Post date:** [February 8, 2011, 4:10pm UTC](https://forum.kirupa.com/t/this-is-why-i-hate-asdoc/319084/1 "2011-02-08T16:10:10Z")

</div>

You don’t need to provide a full 3 line comment for all available properties:

```auto
/** 
 * Defines the name. 
 */ 
public static const NAME:String = "ContentDataProxy";

```

It’s even worse when you really are trying to understand how to use a class, and the ASDocs are included, but either empty or very non-descriptive.

Also, it clutters up documents and makes classes 30% longer. I would much prefer having a separate “MyClass.asdoc” file along with each class just to avoid this. That way, you can still compile the documentation, and it doesn’t take up space in your code.