From: Michal Rokos Date: 2002-05-23T17:56:25+09:00 Subject: Re: Ruby obsolete Hi, On Thu, May 23, 2002 at 02:27:03PM +0900, Yukihiro Matsumoto wrote: > | how about disable obsolete/deprecated things in Ruby. It could > | be good for ext. makers, and who know who else... > I don't take it. a) They are part of the library even though they > will go in the near future. b) If one really care about memory > footprint, he/she won't choose Ruby. I wrote it bad, but it can be as it could work from codesnip. There is #if !defined(RUBY_NO_OBSOLETE) - so it's enabled by default. But if (let's say) ext.maker wants to be sure that his extentension will work in ...... OK - now I don't see any benefit from this :-) Let's forget it. > |(Question: Why is rb_f_getc marked as obsolete and not others?) > What others you meant? There are more global functions than 'gets' (rb_f_*) and they aren't marked as (obsolete|deprecated)... Michal -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Michal Rokos Czech Technical University, Prague E-mail:m.rokos@sh.cvut.cz ICQ:36118339 Jabber:majkl@jabber.sh.cvut.cz -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-