Ask a Question related to Ruby, Design and Development.
-
Nathaniel Talbott #1
Correctly handling the deprecation of rb_enable_super
I'm using a library (ruby-odbc 0.99 to be exact) that calls
rb_enable_super(), which is obsolete as of ruby 1.8.0. Of course, this
causes said library to spit out warnings at me when I use it. I want to
submit a patch to the author to remove the warnings, but I'm not sure of the
correct way to fix it such that the library will still work under 1.6.x. Can
a C/Ruby guru out there give me a hand?
Thanks,
Nathaniel
<:((><
Nathaniel Talbott Guest
-
Variables Not Working correctly..
Im loading variables via loadvariablesnum and im checking the debug and they successfully getinto the _level0 now for some reason in the next... -
how to close correctly?
i have application that i'm the administrator make connection and publish stream and few (the members) are also make connection to me and play... -
css not rendering correctly in IE win
ok, so far, every browser i've tested sans ie win works fine. i'm not concerned with ie mac, and honestly, the audience of this site will probably... -
Can't get Projector to run correctly
I have Director 8.5 and made a movie with flash (5) content. Then I made it into a projector which runs well on XP but it starts up on Win 98 then... -
Not Exporting Correctly
I created a Menu with two behaviors and when I do preview in Fireworks it works fine. But after I export it, only the first behavior is working. ... -
nobu.nokada@softhome.net #2
Re: Correctly handling the deprecation of rb_enable_super
Hi,
At Fri, 12 Sep 2003 05:47:08 +0900,
Nathaniel Talbott wrote:#ifndef HAVE_RB_DEFINE_ALLOC_FUNC> I'm using a library (ruby-odbc 0.99 to be exact) that calls
> rb_enable_super(), which is obsolete as of ruby 1.8.0. Of course, this
> causes said library to spit out warnings at me when I use it. I want to
> submit a patch to the author to remove the warnings, but I'm not sure of the
> correct way to fix it such that the library will still work under 1.6.x. Can
> a C/Ruby guru out there give me a hand?
rb_enable_super(klass, funcname);
#endif
This wouldn't work with transitional versions from 2003/02/09
until 2003/07/16, however, they are deprecated.
--
Nobu Nakada
nobu.nokada@softhome.net Guest
-
Nathaniel Talbott #3
Re: Correctly handling the deprecation of rb_enable_super
[email]nobu.nokada@softhome.net[/email] [mailto:nobu.nokada@softhome.net] wrote:
Thanks, Nobu! Worked like a charm.> #ifndef HAVE_RB_DEFINE_ALLOC_FUNC
> rb_enable_super(klass, funcname);
> #endif
>
> This wouldn't work with transitional versions from 2003/02/09
> until 2003/07/16, however, they are deprecated.
Nathaniel
<:((><
Nathaniel Talbott Guest
-
nobu.nokada@softhome.net #4
Re: Correctly handling the deprecation of rb_enable_super
Hi,
At Fri, 12 Sep 2003 18:43:25 +0900,
Nathaniel Talbott wrote:Now rb_{enable,disable}_super() are dummy macros, so you don't>> > #ifndef HAVE_RB_DEFINE_ALLOC_FUNC
> > rb_enable_super(klass, funcname);
> > #endif
> >
> > This wouldn't work with transitional versions from 2003/02/09
> > until 2003/07/16, however, they are deprecated.
> Thanks, Nobu! Worked like a charm.
have to change the library's source. Just update ruby source
and recompile with it.
--
Nobu Nakada
nobu.nokada@softhome.net Guest
-
ts #5
Re: Correctly handling the deprecation of rb_enable_super
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
n> Now rb_{enable,disable}_super() are dummy macros, so you don't
n> have to change the library's source. Just update ruby source
n> and recompile with it.
Well, some persons are trying to make their libraries work even with
1.8.0, which is released.
p.s. : this problem is well known with bdb ...
Good Luck ...
Guy Decoux
ts Guest



Reply With Quote

