Y
yue_nicholas
HI,
I am writing an extension for Ruby in C++ and as I have more and more
functions, I need to separate them into individual C++ source for
easier maintenance in the long run.
From Programming Ruby, the section on Extending Ruby defines function
as static, if I continue to use the static keyword and the functions
are implemented in separate C++ source file, it would not be visible in
the main ruby method registration file.
How significant is the static keyword when defining functions for use
as Ruby extension?
I had a quick browse of the ruby-netcdf package and noticed that they
do not prefix their function with the static keyword.
Anyone has advice?
Cheers
I am writing an extension for Ruby in C++ and as I have more and more
functions, I need to separate them into individual C++ source for
easier maintenance in the long run.
From Programming Ruby, the section on Extending Ruby defines function
as static, if I continue to use the static keyword and the functions
are implemented in separate C++ source file, it would not be visible in
the main ruby method registration file.
How significant is the static keyword when defining functions for use
as Ruby extension?
I had a quick browse of the ruby-netcdf package and noticed that they
do not prefix their function with the static keyword.
Anyone has advice?
Cheers