pax_global_header 0000666 0000000 0000000 00000000064 13057464420 0014517 g ustar 00root root 0000000 0000000 52 comment=592552a165cc569dac7674cb7fc9de3dc829906f
curlpp-0.8.1/ 0000775 0000000 0000000 00000000000 13057464420 0013032 5 ustar 00root root 0000000 0000000 curlpp-0.8.1/.gitignore 0000664 0000000 0000000 00000001231 13057464420 0015017 0 ustar 00root root 0000000 0000000 *.Po
*.o
*.a
*.la
*.lo
*.Plo
*.dylib
*.lai
Makefile
*~
build/
m4/
CMakeFiles/
examples/example01
examples/example02
examples/example03
examples/example04
examples/example05
examples/example06
examples/example07
examples/example08
examples/example09
examples/example10
examples/example11
examples/example12
examples/example13
examples/example14
examples/example15
examples/example16
examples/example17
examples/example18
examples/example19
examples/example20
examples/example21
examples/example22
examples/example23
examples/example24
examples/example25
*.exe
CMakeCache.txt
conanbuildinfo.cmake
conaninfo.txt
bin/
curlpp-0.8.1/.hgignore 0000664 0000000 0000000 00000000472 13057464420 0014640 0 ustar 00root root 0000000 0000000 (^|/)\.svn($|/)
(^|/)\.hg($|/)
(^|/)\.hgtags($|/)
^curlpp-svn.log$
^tailor.state$
^tailor.state.old$
^tailor.state.journal$
.*\.o
.*\.lo
.*\.a
.*\.la
.*\.Plo
.*\.Po
#.*#$
Makefile$
Makefile.in$
include/curlpp/config.h.in
include/curlpp/config.h
^examples/example[0-9]*$
aclocal.m4$
.dylib$
curlpp.pc$
curlpp.spec$
curlpp-0.8.1/.travis.yml 0000664 0000000 0000000 00000002073 13057464420 0015145 0 ustar 00root root 0000000 0000000 language: cpp
# precise gcc doesn't have c++11 support
matrix:
include:
- os: linux
dist: trusty
compiler: clang
env: NAME="trusty"
- os: linux
dist: trusty
compiler: gcc
env: NAME="trusty"
- os: linux
dist: precise
compiler: clang
env: NAME="precise"
- os: osx
osx_image: xcode7.2
- os: osx
compiler: clang
- os: osx
compiler: gcc
addons:
apt:
packages:
- libcurl4-openssl-dev
before_script:
- mkdir build && cd build
- cmake ../
script:
- make && sudo make install
- cd ../examples && mkdir build && cd build
- cmake ../
- make
install:
- echo install-----------------------------------------------------------------
# Download and install libcurl
- if [[ $TRAVIS_OS_NAME == "osx" ]]; then
brew update;
brew install curl;
fi
# install cmake 3.2 for precise
- if [[ $NAME == "precise" ]]; then
sudo add-apt-repository ppa:george-edison55/precise-backports --yes;
sudo apt-get update;
sudo apt-get install cmake-data cmake;
fi curlpp-0.8.1/CMakeLists.txt 0000664 0000000 0000000 00000010404 13057464420 0015571 0 ustar 00root root 0000000 0000000 project(curlpp)
# In response to CMake 3.0 generating warnings regarding policy CMP0042,
# the OSX RPATH settings have been updated per recommendations found
# in the CMake Wiki:
# http://www.cmake.org/Wiki/CMake_RPATH_handling#Mac_OS_X_and_the_RPATH
if(POLICY CMP0042)
cmake_policy(SET CMP0042 NEW) # MACOSX_RPATH
set(CMAKE_MACOSX_RPATH TRUE)
endif()
# for unix platform, define install directories.
include(GNUInstallDirs)
if(WIN32)
# cmake 3.4 is required for CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS
cmake_minimum_required(VERSION 3.4)
# c++ 11 support from cmake 3.4 or newer
set(CMAKE_CXX_STANDARD 11) # C++11...
set(CMAKE_CXX_STANDARD_REQUIRED ON) #...is required...
set(CMAKE_CXX_EXTENSIONS OFF) #...without compiler extensions like gnu++11
set(CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS ON)
else()
if (${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION} VERSION_LESS 3.1)
cmake_minimum_required(VERSION 2.8)
# c++11 support for cmake 2.8.12 - 3.0.x
#
# for non-windows platform we try to keep cmake 2.8 support
# since entreprise distribution tends to have 2.8 version.
add_compile_options(-std=c++11)
else()
# c++ 11 support from cmake 3.1 or newer
set(CMAKE_CXX_STANDARD 11) # C++11...
set(CMAKE_CXX_STANDARD_REQUIRED ON) #...is required...
set(CMAKE_CXX_EXTENSIONS OFF) #...without compiler extensions like gnu++11
endif()
endif()
# Conan.io integration
if(EXISTS ${CMAKE_CURRENT_SOURCE_DIR}/conanbuildinfo.cmake)
include(${CMAKE_CURRENT_SOURCE_DIR}/conanbuildinfo.cmake)
conan_basic_setup()
endif()
# extra (pkg-config-related files)
add_subdirectory(extras)
#########################################################################################
# Look for dependencies
# Documented at https://cmake.org/cmake/help/v3.0/module/FindCURL.html?highlight=curlpp
# Seems simple.
message(STATUS "Looking for CURL")
include(FindCURL)
find_package(CURL REQUIRED)
if(CURL_FOUND)
message(STATUS "Found CURL version: ${CURL_VERSION_STRING}")
message(STATUS "Using CURL include dir(s): ${CURL_INCLUDE_DIRS}")
message(STATUS "Using CURL lib(s): ${CURL_LIBRARIES}")
else()
message(FATAL_ERROR "Could not find CURL")
endif()
# All following targets should search these directories for headers
include_directories(
${CMAKE_CURRENT_SOURCE_DIR}/include
${CURL_INCLUDE_DIRS}
)
#########################################################################################
# Define Targets
# If building on windows, install path will be in build/winbuild
if(CMAKE_SYSTEM MATCHES "Windows")
set(CMAKE_INSTALL_PREFIX "winbuild")
endif()
file(GLOB_RECURSE HeaderFileList "${CMAKE_CURRENT_SOURCE_DIR}/include/*")
file(GLOB_RECURSE SourceFileList "${CMAKE_CURRENT_SOURCE_DIR}/src/*")
add_library(${PROJECT_NAME} SHARED ${HeaderFileList} ${SourceFileList})
target_link_libraries(${PROJECT_NAME} ${CURL_LIBRARIES} ${CONAN_LIBS})
set_target_properties(${PROJECT_NAME} PROPERTIES SOVERSION 1 VERSION 1.0.0)
add_library(${PROJECT_NAME}_static STATIC ${HeaderFileList} ${SourceFileList})
# Make sure that on unix-platforms shared and static libraries have
# the same root name, but different suffixes.
#
# (solution taken from https://cmake.org/Wiki/CMake_FAQ#How_do_I_make_my_shared_and_static_libraries_have_the_same_root_name.2C_but_different_suffixes.3F)
#
# Making shared and static libraries have the same root name, but different suffixes
SET_TARGET_PROPERTIES(${PROJECT_NAME}_static PROPERTIES OUTPUT_NAME ${PROJECT_NAME})
# Now the library target "curlpp_static" will be named "curlpp.lib" with MS tools.
# This conflicts with the "curlpp.lib" import library corresponding to "curlpp.dll",
# so we add a "lib" prefix (which is default on other platforms anyway):
SET_TARGET_PROPERTIES(${PROJECT_NAME}_static PROPERTIES PREFIX "lib")
target_link_libraries(${PROJECT_NAME}_static ${CURL_LIBRARIES} ${CONAN_LIBS})
# install headers
install(DIRECTORY include/utilspp/ DESTINATION "${CMAKE_INSTALL_INCLUDEDIR}/utilspp")
install(DIRECTORY include/curlpp/ DESTINATION "${CMAKE_INSTALL_INCLUDEDIR}/curlpp")
install(TARGETS ${PROJECT_NAME} ${PROJECT_NAME}_static
RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR})
curlpp-0.8.1/CNAME 0000664 0000000 0000000 00000000016 13057464420 0013575 0 ustar 00root root 0000000 0000000 www.curlpp.org curlpp-0.8.1/Readme.md 0000664 0000000 0000000 00000004312 13057464420 0014551 0 ustar 00root root 0000000 0000000 [](https://opensource.org/licenses/MIT) [](https://travis-ci.org/jpbarrette/curlpp) [](https://ci.appveyor.com/project/jpbarrette/curlpp)
# Description
[cURLpp](http://www.curlpp.org) is a C++ wrapper for libcURL. libcURL is described as:
a free and easy-to-use client-side URL transfer library, supporting FTP, FTPS, HTTP, HTTPS, GOPHER, TELNET, DICT, FILE and LDAP. libcurl supports HTTPS certificates, HTTP POST, HTTP PUT, FTP uploading, kerberos, HTTP form based upload, proxies, cookies, user+password authentication, file transfer resume, http proxy tunneling and more!
libcurl is highly portable, it builds and works identically on numerous platforms, including Solaris, NetBSD, FreeBSD, OpenBSD, Darwin, HPUX, IRIX, AIX, Tru64, Linux, Windows, Amiga, OS/2, BeOs, Mac OS X, Ultrix, QNX, OpenVMS, RISC OS, Novell NetWare, DOS and more...
libcurl is free, thread-safe, IPv6 compatible, feature rich, well supported and fast.
First, I need to quote Daniel Stenberg, the maintener of libcURL:
You can use libcURL instantly from within your C++ programs. You don't need cURLpp for that, cURLpp just adds an OO'ified layer that libcURL doesn't normally provide. It means that you need to be sure that you need, or want, cURLpp features. If not, I suggest to use directly the libcURL library. So, what are thoses features that cURLpp offers?
* You can query handles for option values (version 0.5.x and newer only).
* It use the C++ standard library structures instead of home made ones.
* It is exception safe.
* It is type safe.
# Download
Latest version is available on GitHub [here](https://github.com/jpbarrette/curlpp/releases/latest).
# Documentation
The programming guide is [here](https://github.com/jpbarrette/curlpp/tree/master/doc/guide.pdf). This guide is greatly inspired by the libcURL guide, that I strongly suggest to read. There's also some examples in the "[examples](http://github.com/jpbarrette/curlpp/tree/master/examples)/" source directory of cURLpp.
curlpp-0.8.1/_config.yml 0000664 0000000 0000000 00000000033 13057464420 0015155 0 ustar 00root root 0000000 0000000 theme: jekyll-theme-minimal curlpp-0.8.1/appveyor.yml 0000664 0000000 0000000 00000002566 13057464420 0015433 0 ustar 00root root 0000000 0000000 version: '0.7.4.{build}'
environment:
matrix:
- PRJ_GEN: "Visual Studio 11 2012 Win64"
BDIR: msvc2012
PRJ_CFG: Release
PRJ_GEN_VERSION: 11
- PRJ_GEN: "Visual Studio 12 2013 Win64"
BDIR: msvc2013
PRJ_CFG: Release
PRJ_GEN_VERSION: 12
- PRJ_GEN: "Visual Studio 14 2015 Win64"
BDIR: msvc2015
PRJ_CFG: Release
PRJ_GEN_VERSION: 14
- PRJ_GEN: "Visual Studio 11 2012 Win64"
BDIR: msvc2012
PRJ_CFG: Debug
PRJ_GEN_VERSION: 11
- PRJ_GEN: "Visual Studio 12 2013 Win64"
BDIR: msvc2013
PRJ_CFG: Debug
PRJ_GEN_VERSION: 12
- PRJ_GEN: "Visual Studio 14 2015 Win64"
BDIR: msvc2015
PRJ_CFG: Debug
PRJ_GEN_VERSION: 14
install:
- cmd: echo "Downloading conan..."
- cmd: set PATH=%PATH%;%PYTHON%/Scripts/
- cmd: pip.exe install conan
- cmd: conan user # Create the conan data directory
- cmd: conan --version
build_script:
- mkdir build.%BDIR%
- IF %PRJ_GEN_VERSION% == 11 call "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\vsvars32.bat"
- conan install --build=missing -s compiler="Visual Studio" -s compiler.version=%PRJ_GEN_VERSION% -s build_type=%PRJ_CFG% .
- cd build.%BDIR%
- cmake .. -G"%PRJ_GEN%"
- cmake --build . --config %PRJ_CFG% --clean-first
curlpp-0.8.1/conanfile.txt 0000664 0000000 0000000 00000000074 13057464420 0015532 0 ustar 00root root 0000000 0000000 [requires]
libcurl/7.50.3@lasote/stable
[generators]
cmake
curlpp-0.8.1/doc/ 0000775 0000000 0000000 00000000000 13057464420 0013577 5 ustar 00root root 0000000 0000000 curlpp-0.8.1/doc/AUTHORS 0000664 0000000 0000000 00000000425 13057464420 0014650 0 ustar 00root root 0000000 0000000 Eric Lavigne (erlavigne at wanadoo.fr)
Jean-Philippe Barrette-LaPierre (jpb at rrette.com)
Thanks to some patch providers:
Thomas Boutry
Jonathan Wakely
Peter Krumins
Ben Golding
Glenn
Hoef Jan
Gisle Vanem
Paul Lacy
Nicolas Le Goff
curlpp-0.8.1/doc/LICENSE 0000664 0000000 0000000 00000002073 13057464420 0014606 0 ustar 00root root 0000000 0000000 Copyright (c) <2002-2004>
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files
(cURLpp), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
curlpp-0.8.1/doc/README.win32 0000664 0000000 0000000 00000026432 13057464420 0015427 0 ustar 00root root 0000000 0000000 Read the README file first.
As of version 0.6.0 curlpp has been built and run on win32.
Information contained in this file does not apply to cygwin builds.
curlpp has been tested on
Microsoft Visual C++ 7.1 (2003), (by Giuseppe "Cowo" Corbelli)
Microsoft Visual C++ 8.0 (2005), (by Andrei Korostelev)
Microsoft Visual C++ 9.0 (2008), (by Piotr Dobrogost)
but any modern C++ compiler should do the job.
BUILDING CURLPP WITH MSVC
-------------------------
BUILDING CURLPP
You can build curlpp in three different ways
A. from within MS Visual Studio IDE
B. using msbuild tool and solution files
C. using namke and makefile
A. and B.
In case of A. and B. first you have to create solution files for your version of MS Visual Studio.
To do this use win32\create-vc-solution.bat batch file with one of the following parameters:
7.1, for Visual Studio 2003
8, for Visual Studio 2005
9, for Visual Studio 2008
This batch file needs sed to be run successfully. You can download sed for win32 platform here
http://gnuwin32.sourceforge.net/packages/sed.htm
A. Building from within IDE
Choosing configuration
Choose configuration you would like to build. What configuration you want depens on three aspects.
1. Weather you want to build dynamic library (dll) or static library (lib).
Choose configuration with DynamicLib or StaticLib prefix.
2. Weather you want to build debug or release version of the library.
Choose configuration with Debug or Release infix.
3. Weather you want static runtime library (RTL) to be used by curlpp or dynamic one.
Choose configuration with StaticRTL or DynamicRTL suffix.
Names' suffixes of output .lib and .dll files depend on the all three choices.
MTd - dynamic, debug, static RTL
MT - dynamic, release, static RTL
MDd - dynamic, debug, dynamic RTL
MD - dynamic, release, dynamic RTL
staticMTd - static, debug, static RTL
staticMT - static, release, static RTL
staticMDd - static, debug, dynamic RTL
staticMD - static, release, dynamic RTL
We will refer to these suffixes and types of libraries as "build category" further in this document.
Setting include directory
If you are building curlpp using the original directory structure then you don't need to set value of user macro
CURLPP_INCLUDE_PATH (by default ".\include"). If however you modified the original directory structure you have
to set value of this macro to the path, where you have curlpp source files.
Setting output directory
The output files will be placed in a directory set in CURLPP_LIB_PATH user macro (by default ".out\lib").
B. Building using msbuild
Open a command prompt and change folder to the root of curlpp tree.
set LIBCURL_PATH=/where/curl/is/installed
set OPENSSL_PATH=/where/openssl/is/installed (only if you have libcurl with ssl support and ssl installed)
msbuild curlpp.sln /t:Rebuild /p:Configuration=
where is one of
- DynamicLibDebugDynamicRTL
- DynamicLibDebugStaticRTL
- DynamicLibReleaseDynamicRTL
- DynamicLibReleaseStaticRTL
- StaticLibDebugDynamicRTL
- StaticLibDebugStaticRTL
- StaticLibReleaseDynamicRTL
- StaticLibReleaseStaticRTL
Output files will be placed in a directory set in CURLPP_LIB_PATH.
Any of DynamicLib* configurations will build a .dll library file and a .lib library import file.
Any of StaticLib* configurations will build the .lib static (inline) library.
Any of *Debug* configurations will in addition build a .pdb Program Database file.
C. Building using nmake
Open a command prompt and change folder to the root of curlpp tree.
Run nmake /f makefile with the following parameters
BUILD_CFG=[dynamic|static]-[debug|release]
RTLIB_CFG=[dynamic|static]-[debug|release]
LIBCURL_CFG=[dynamic|static]-[debug|release]
All options are optional.
Default for BUILD_CFG is dynamic-release.
Default for others is the value of BUILD_CFG.
Edit the LIBCURL_PATH or set LIBCURL_PATH envvar!
NOTES
Linking with libcurl
All versions of this library need libcurl (c library) include files to compile and lib file to link successfully.
To build curlpp you first have to set value of LIBCURL_PATH user macro to your installation of libcurl.
This macro is used in the project file for VC9 to find include and lib files of libcurl.
Steps to set user macro. Select View/Property Manager, double-click curlpp property sheet, go to
Common Properties/User Macros/, double-click name of macro you want to modify, modify it and click OK.
Filename of libcurl's lib file should be in the form libcurlX.lib where X denotes build category chosen for curlpp.
(see Linking with RTL)
If it has different name you have to change .lib filename in
Project properties\Librarian\Additional Dependencies (when building static library)
or
Project properties\Linker\Input\Additional Dependencies (when building dynamic library).
Linking with static libcurl
If you are not going to use libcurl as a dll and you would like to include it into your library/executable by
linking to static version of libcurl you have to define preprocessor symbol CURL_STATICLIB. You can do it in
Project/Properties/C/C++/Preprocessor/Preprocessor Definitions.
By default all StaticLib* configurations define this symbol. If for some reason you would like to build static
curlpp library which links do dynamic libcurl library you have to remove CURL_STATICLIB define.
Linking with RTL
You have to link with libcurl which uses RTL in the same way as you are going to use RTL in curlpp lib.
Refering to build categories defined earlier in section "Choosing configuration" both libcurl and curlpp
must have the same build category.
If you are going to use dynamic RTL in curlpp (MD[x]), use libcurl which also uses dynamic RTL (MD[x]).
If you are going to use static RTL in curlpp (MT[x]), use libcurl which also uses static RTL (MT[x]).
You can use debug build of libcurl (MDd or MTd) in the release build of curlpp (MD or MT) and
you can use release build of libcurl (MD or MT) in the debug build of curlpp (MDd or MTd).
However you shouldn't do this.
Building self-contained version of the library
curlpp is mostly a template library. For this reason during build of it, only non template entities are placed in the
.lib and .dll files. Most of the library's features used in your application causes code generation during compilation
of _your project_ and the code is placed in your executable. This is often not desirable. If you want to build
the curlpp as self-contained library (one which has all code called by clients in its .lib and .dll files) you can
define preprocesor symbol CURL_SELF_CONTAINED. In this case curlpp uses explicit template instantiation (all such
instantiantions are placed in separte .ins files) to force generating code into .lib and .dll files. You have to
define this preprocesor symbol during build of your application to avoid including templates' definitions as they
are not needed in this phase. If you get linker errors connected with curlpp features when using self-contained
version of the library it's because there are some missing explicit instantiantions. Please let us know if it happens.
Using curlpp in .NET applications
If you are going to use curlpp library in a .NET project you have to use dynamic RTL.
This is because all .NET applications must use dynamic RTL and if your application uses curlpp,
the library itself has to use dynamic RTL as well.
Additional dependencies
To build examples (and your project as well) you need the following Windows lib files to link successfully
WSock32.lib, Wldap32.lib
These files comes with WindowsSDK. Macro $(WIN_SDK_DIR) (by default $(WindowsSdkDir)) is used in the properties
sheet file curlpp.examples.VC9.vsprops by VC9 solution to find these libraries.
Linking with OpenSSL
If you have libcurl compiled with OpenSSL support and want to have support for OpenSSL in curlpp as well
you have to set value of OPENSSL_PATH user macro to your installation of OpenSSL before building curlpp.
This variable is used in the project file for VC9 to find include and lib files of OpenSSL.
Steps to set user macro. Select View/Property Manager, double-click curlpp property sheet, go to
Common Properties/User Macros/, double-click name of macro you want to modify, modify it and click OK.
You have to link with OpenSSL which uses RTL in the same way as you are going to use RTL in curlpp lib.
Refering to build categories defined earlier in section "Choosing configuration" both OpenSSL and curlpp
must have the same build category.
Filenames of OpenSSL lib files should be in the form libeay32X.lib and ssleay32X.lib, where X denotes
build category chosen for curlpp. You have to add both this filenames to
Project properties\Librarian\Additional Dependencies (when building static library)
or
Project properties\Linker\Input\Additional Dependencies (when building dynamic library).
If you need OpenSSL for Windows platform take a look at http://www.slproweb.com/products/Win32OpenSSL.html
If you installed OpenSSL downloaded from the above link you'll find .lib files of all four build categories
in the /lib/vc directory.
Building with support for Boost
curlpp has ability to use some features from the Boost library. If you want to build curlpp with support for Boost
you have to set value of BOOST_PATH user macro to your installation of Boost before building curlpp.
This variable is used in the project file for VC9 to find include files of Boost.
You also have to define preprocessor symbol HAVE_BOOST. You can do it in
Project/Properties/C/C++/Preprocessor/Preprocessor Definitions.
Project propery sheets
All user macros like LIBCURL_PATH, OPENSSL_PATH, BOOST_PATH, CURLPP_INCLUDE_PATH, CURLPP_LIB_PATH, WIN_SDK_DIR,
CURLPP_EXAMPLES_OUT_DIR, etc.
are defined in project property sheet files named
curlpp.common.vsprops - options and macros used during build of library itself and during build of examples
curlpp.lib.vsprops - options and macros used during build of library itself
curlpp.examples.vsprops - options and macros used during build of examples
Compiler warnings
There are a few kinds of compiler warnings which we haven't managed to remove.
warning C4251: class X needs to have dll-interface to be used by clients of class Y
warning C4275: non dll-interface class X used as base for dll-interface class Y
warning C4512: X : assignment operator could not be generated
warning C4661: methodX : no suitable definition provided for explicit template instantiation request
BUILDING CURLPP EXAMPLES
Your can either build the examples from MS Visual Studio IDE or from the command line from within examples folder:
nmake -f Makefile.msvc all
or
nmake -f Makefile.msvc exampleXY
to build example XY
Giuseppe "Cowo" Corbelli, cowo at lugbs dot linux dot it
Andrei Korostelev, andrei at korostelev dot net
Piotr Dobrogost, pd.curlpp.org (November 2008 - March 2009) curlpp-0.8.1/doc/TODO 0000664 0000000 0000000 00000000313 13057464420 0014264 0 ustar 00root root 0000000 0000000 - Need to fix the OptionList::print function.
- Need to put WriteStream and ReadStream to be exception safe.
- Need to put WriteStream and ReadStream to be exception safe.
- Get rid of example 18 and 20
curlpp-0.8.1/doc/guide.pdf 0000664 0000000 0000000 00000272000 13057464420 0015370 0 ustar 00root root 0000000 0000000 %PDF-1.4
3 0 obj <<
/Length 1612
/Filter /FlateDecode
>>
stream
xڕWK6WV%}lHPA(l%Cw^caW3p8w7yn*Ro,˸(7Oi bu<l(Vg;5){48
4פ(l,L}lͰ.TLSnI%ɶHO@N-ްI0eaYf 4CK5r@,t}:Fth6NcRFu-+c8{EL~i o.*XL*UH@
Ux"GhZWO28v|B=䊡a∡=/ٚo4ls"]#ƤFkBQ@ZmNx}D IHH &<'P0ئINO%ӡ%ߡQ~j '+r;|
}<
D߾]gI%2,(Xo/G ,0-+жcz9s;})}۷e&%[\Pqz\R@d 1g