@@ -, +, @@
---
codeblocks/libsphinx.cbp | 2 +-
doc/sphinx.html | 8 ++++----
doc/sphinx.txt | 8 ++++----
doc/sphinx.xml | 8 ++++----
src/CMakeLists.txt | 2 +-
src/Makefile.am | 2 +-
src/Makefile.in | 2 +-
src/{sphinxudf.c => sphinxudf.cpp} | 4 ++--
win/libsphinx12.vcxproj | 2 +-
win/libsphinx13.vcxproj | 2 +-
10 files changed, 20 insertions(+), 20 deletions(-)
rename src/{sphinxudf.c => sphinxudf.cpp} (99%)
--- a/codeblocks/libsphinx.cbp
+++ a/codeblocks/libsphinx.cbp
@@ -74,7 +74,7 @@
#include "sphinxudf.h"
, like in the example,
should be completely sufficient, too. However, if you're writing a ranking function and
need to access the ranking signals (factors) data from within the UDF, you will
-also need to compile and link with src/sphinxudf.c
(also
+also need to compile and link with src/sphinxudf.cpp
(also
available in our source code), because the implementations
of the fuctions that let you access the signal data from within the UDF reside
in that file.
-Both sphinxudf.h
header and sphinxudf.c
+Both sphinxudf.h
header and sphinxudf.cpp
are standalone. So you can copy around those files only; they do not depend
on any other bits of Sphinx source code.
@@ -3888,8 +3888,8 @@ Just as with UDFs, you want to include src/sphinxudf.hsrc/sphinxudf.c
. However, as of 2.2.2-beta all
-the functions implemented in sphinxudf.c
are about
+src/sphinxudf.cpp
. However, as of 2.2.2-beta all
+the functions implemented in sphinxudf.cpp
are about
unpacking the PACKEDFACTORS() blob, and no plugin types are exposed to that
kind of data. So currently, you would never need to link with the C-file,
just the header would be sufficient. (In fact, if you copy over the
--- a/doc/sphinx.txt
+++ a/doc/sphinx.txt
@@ -4280,11 +4280,11 @@ related structures and types. For most UDFs and plugins, a mere #include
"sphinxudf.h", like in the example, should be completely sufficient, too.
However, if you're writing a ranking function and need to access the
ranking signals (factors) data from within the UDF, you will also need to
-compile and link with src/sphinxudf.c (also available in our source code),
+compile and link with src/sphinxudf.cpp (also available in our source code),
because the implementations of the fuctions that let you access the signal
data from within the UDF reside in that file.
-Both sphinxudf.h header and sphinxudf.c are standalone. So you can copy
+Both sphinxudf.h header and sphinxudf.cpp are standalone. So you can copy
around those files only; they do not depend on any other bits of Sphinx
source code.
@@ -4490,8 +4490,8 @@ and plugin; that is up to you.
Just as with UDFs, you want to include src/sphinxudf.h header file. At the
very least, you will need the SPH_UDF_VERSION constant to implement
a proper version function. Depending on the specific plugin type, you might
-or might not need to link your plugin with src/sphinxudf.c. However, as of
-2.2.2-beta all the functions implemented in sphinxudf.c are about unpacking
+or might not need to link your plugin with src/sphinxudf.cpp. However, as of
+2.2.2-beta all the functions implemented in sphinxudf.cpp are about unpacking
the PACKEDFACTORS() blob, and no plugin types are exposed to that kind of
data. So currently, you would never need to link with the C-file, just the
header would be sufficient. (In fact, if you copy over the UDF version
--- a/doc/sphinx.xml
+++ a/doc/sphinx.xml
@@ -4094,13 +4094,13 @@ header file definitions of a few UDF related structures and types. For most
UDFs and plugins, a mere #include "sphinxudf.h"
, like in the example,
should be completely sufficient, too. However, if you're writing a ranking function and
need to access the ranking signals (factors) data from within the UDF, you will
-also need to compile and link with