https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112010-04-16T19:10:33ZRuby Issue Tracking SystemRuby master - Bug #2059: Marking internal functions as internalhttps://bugs.ruby-lang.org/issues/2059?journal_id=102332010-04-16T19:10:33Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Rejected</i></li></ul><p>=begin<br>
Hi,</p>
<blockquote>
<p>All internal (extern) functions should be marked as internal<br>
in Doxygen comments before 1.9.2's release.</p>
</blockquote>
<p>I strongly object. If a function has no document, it should be<br>
considered as function just for internal, by default. We cannot<br>
guarantee compatibility of non-documented functions completely.<br>
Authors of ext library must use them at the risk.</p>
<p>Indeed, many functions have no document, even if the function is<br>
really needed (and actually used) by many ext library. The fact<br>
is unfortunate.<br>
We should respect compatiblity of "behavior" as far as possible.</p>
<p>However, undocumented function is undocumented function.</p>
<p>Anyway, this is never a bug. So I reject this ticket.</p>
<p>Ruby's C API should be reorganized and documented, towards 2.0.<br>
Welcome volunteers.</p>
<p>--<br>
Yusuke Endoh <a href="mailto:mame@tsg.ne.jp" class="email">mame@tsg.ne.jp</a><br>
=end</p>