Project

General

Profile

Bug #2059

Marking internal functions as internal

Added by yugui (Yuki Sonoda) about 11 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
ruby -v:
-
Backport:

Description

=begin
All internal (extern) functions should be marked as internal in Doxygen comments before 1.9.2's release.
=end

#1

Updated by mame (Yusuke Endoh) over 10 years ago

  • Status changed from Open to Rejected

=begin
Hi,

All internal (extern) functions should be marked as internal
in Doxygen comments before 1.9.2's release.

I strongly object. If a function has no document, it should be
considered as function just for internal, by default. We cannot
guarantee compatibility of non-documented functions completely.
Authors of ext library must use them at the risk.

Indeed, many functions have no document, even if the function is
really needed (and actually used) by many ext library. The fact
is unfortunate.
We should respect compatiblity of "behavior" as far as possible.

However, undocumented function is undocumented function.

Anyway, this is never a bug. So I reject this ticket.

Ruby's C API should be reorganized and documented, towards 2.0.
Welcome volunteers.

--
Yusuke Endoh mame@tsg.ne.jp
=end

Also available in: Atom PDF