vm.c: always export rb_frame_method_id_and_class

Functions declared in include/ruby/backward.h is exported only when
the condition `!defined RUBY_EXPORT && !defined RUBY_NO_OLD_COMPATIBILITY`
is met (i.e. included by include/ruby/ruby.h).

So if it is not the case when ruby is built, this will not be exported.
This was not intentional at r60994.

[Bug #14192]

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61296 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
k0kubun 2017-12-16 13:02:25 +00:00
Родитель f319aa859d
Коммит 316f58076d
1 изменённых файлов: 1 добавлений и 1 удалений

2
vm.c
Просмотреть файл

@ -2049,7 +2049,7 @@ rb_ec_frame_method_id_and_class(const rb_execution_context_t *ec, ID *idp, ID *c
return rb_vm_control_frame_id_and_class(ec->cfp, idp, called_idp, klassp); return rb_vm_control_frame_id_and_class(ec->cfp, idp, called_idp, klassp);
} }
int RUBY_FUNC_EXPORTED int
rb_frame_method_id_and_class(ID *idp, VALUE *klassp) rb_frame_method_id_and_class(ID *idp, VALUE *klassp)
{ {
return rb_ec_frame_method_id_and_class(GET_EC(), idp, 0, klassp); return rb_ec_frame_method_id_and_class(GET_EC(), idp, 0, klassp);