Description:
The user manual describes how to use Visual Studio 6 "dsp"
files from the source distribution "VC++Files/udf_example"
directory. Or rather "source repository". There are so many
problems with this
1. If a supported way of extending, it should be in the source
package (at least, more later). As the dsp files are now
obsolete and not part of that package, also the UDF
example is gone.
, 2. We no longer support Visual Studio 6 in 4.1 and up, so
there are no "dsp" project files as described in the user
manual. And no need for renaming "udf_example.cc"
to "udf_example.cpp". Now we might want to let VS6
users to create UDFs, if so we need to include the dsp
files and test that this works.
In any case, we lack "vcproj" files for Visual Studio .NET
2003 and 2005, and the changes needed in the manual.
3. An UDF is a shared object, on Windows it should likely
be an DLL. So there should not be a dependency on
having a complete source repository or even a source
package (even if that is kind of ok as a limitation).
I would suggest that needed headers are moved to
be just one, and that this header and the UDF example
is part of the binary distribution, and not only the
"noinstall" package, also the installer package.
This is not a strong requirement, part of the source
package is ok even if strictly someone adding an UDF
should not have to know anything about the server
build itself.
4. The user manual talks about the UDF file extension
to be ".so". This might not even be true for all
UNIX platforms (even if ok to force it to be), but on
Windows it should be ".dll" if it is a DLL. Or
alternativenly something completely different on
both UNIX and Windows.
How to repeat:
Inspect the user manual, the BitKeeper tree and the
source distribution.
Description: The user manual describes how to use Visual Studio 6 "dsp" files from the source distribution "VC++Files/udf_example" directory. Or rather "source repository". There are so many problems with this 1. If a supported way of extending, it should be in the source package (at least, more later). As the dsp files are now obsolete and not part of that package, also the UDF example is gone. , 2. We no longer support Visual Studio 6 in 4.1 and up, so there are no "dsp" project files as described in the user manual. And no need for renaming "udf_example.cc" to "udf_example.cpp". Now we might want to let VS6 users to create UDFs, if so we need to include the dsp files and test that this works. In any case, we lack "vcproj" files for Visual Studio .NET 2003 and 2005, and the changes needed in the manual. 3. An UDF is a shared object, on Windows it should likely be an DLL. So there should not be a dependency on having a complete source repository or even a source package (even if that is kind of ok as a limitation). I would suggest that needed headers are moved to be just one, and that this header and the UDF example is part of the binary distribution, and not only the "noinstall" package, also the installer package. This is not a strong requirement, part of the source package is ok even if strictly someone adding an UDF should not have to know anything about the server build itself. 4. The user manual talks about the UDF file extension to be ".so". This might not even be true for all UNIX platforms (even if ok to force it to be), but on Windows it should be ".dll" if it is a DLL. Or alternativenly something completely different on both UNIX and Windows. How to repeat: Inspect the user manual, the BitKeeper tree and the source distribution.