2015-01-19 14:43:59 +01:00
POCO C++ Libraries
2012-11-11 10:42:13 +01:00
==================
2012-10-24 21:39:17 +02:00
2015-01-19 14:43:59 +01:00
Build Status
------------
- Travis: [![Travis Build Status ](https://travis-ci.org/pocoproject/poco.png?branch=develop )](https://travis-ci.org/pocoproject/poco)
- AppVeyor: [![AppVeyor Build Status ](https://ci.appveyor.com/api/projects/status/7iyrx3f233s3akae )](https://ci.appveyor.com/project/obiltschnig/poco)
2013-06-05 06:16:05 +02:00
POrtable COmponents C++ Libraries are:
--------------------------------------
- A collection of C++ class libraries, conceptually similar to the Java Class Library, the .NET Framework or Apple’ s Cocoa.
- Focused on solutions to frequently-encountered practical problems.
- Focused on ‘ internet-age’ network-centric applications.
- Written in efficient, modern, 100% ANSI/ISO Standard C++.
- Based on and complementing the C++ Standard Library/STL.
- Highly portable and available on many different platforms.
- Open Source, licensed under the Boost Software License.
2012-10-24 22:15:56 +02:00
2014-10-14 03:26:02 +02:00
----
To start using POCO, see the [Guided Tour ](http://pocoproject.org/docs-1.5.3/00100-GuidedTour.html ) and [Getting Started ](http://pocoproject.org/docs-1.5.3/00200-GettingStarted.html ) documents.
2013-06-05 06:16:05 +02:00
----
POCO has an active user and contributing community, please visit our [web site ](http://pocoproject.org ), [forum ](http://pocoproject.org/forum ) and [blog ](http://pocoproject.org/blog ).
Answers to POCO-related questions can also be found on [Stack Overflow ](http://stackoverflow.com/questions/tagged/poco-libraries ).
----
2014-10-14 03:26:52 +02:00
In regards to Boost, in spite of some functional overlapping,
POCO is best thought of as a Boost complement (rather than replacement).
Side-by-side use of Boost and POCO is a very common occurence.
2013-06-05 06:16:05 +02:00
When contributing to POCO, please adhere to our [coding styleguide ](http://www.appinf.com/download/CppCodingStyleGuide.pdf ).
We use the branching model described [here ](http://nvie.com/posts/a-successful-git-branching-model/ ).
2012-11-11 10:42:13 +01:00
All text file line endings in the repository must be Unix-style (LF).
This includes Visual Studio project and solution files (.sln, .vcproj, .vcxproj, .vcxproj.filters).