thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-22 15:42:02 +00:00
Code Issues Packages Projects Releases Wiki Activity
8144c28c3b
ClickHouse/base/poco
History
Robert Schulze 8144c28c3b
Fix spelling
2023-02-10 10:49:55 +00:00
..
Crypto Fix spelling 2023-02-10 10:49:55 +00:00
Data Fix spelling 2023-02-10 10:49:55 +00:00
Foundation Fix spelling 2023-02-10 10:49:55 +00:00
JSON Fix spelling 2023-02-10 10:49:55 +00:00
MongoDB Fix warnings in poco mongodb 2023-02-08 11:26:36 +00:00
Net Fix spelling 2023-02-10 10:49:55 +00:00
NetSSL_OpenSSL Fix spelling 2023-02-10 10:49:55 +00:00
patches/AIX Move poco to base/poco/ (#46075) 2023-02-08 12:04:11 +01:00
Redis Fix spelling 2023-02-10 10:49:55 +00:00
Util Fix spelling 2023-02-10 10:49:55 +00:00
XML Fix spelling 2023-02-10 10:49:55 +00:00
CMakeLists.txt More fine-granular warning relaxation 2023-02-08 11:21:59 +00:00
LICENSE Move poco to base/poco/ (#46075) 2023-02-08 12:04:11 +01:00
README.md Move poco to base/poco/ (#46075) 2023-02-08 12:04:11 +01:00

README.md

alt text

Travis Build Status Build status CII Best Practices

POCO (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, from embedded to server.
  • Open Source, licensed under the Boost Software License.

alt text

To start using POCO, see the Guided Tour and Getting Started documents.

POCO has an active user and contributing community, please visit our web site and blog. Answers to POCO-related questions can also be found on Stack Overflow.

Please see CONTRIBUTING for submitting contributions, bugs reports, feature requests or security issues.

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 occurrence.