actor-framework: c++ actor 框架

代码拉取完成,页面将自动刷新

richgiteeai

Watch

不关注关注所有动态仅关注版本发行动态关注但不提醒动态

1 Star 1 Fork 1

StarBeats/actor-framework

代码 Issues 0 Pull Requests 0 Wiki 统计流水线

服务

加入 Gitee

与超过 1400万开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)

免费加入

已有帐号? 立即登录

克隆/下载

HTTPS SSH SVN SVN+SSH 下载ZIP

提示

下载代码请复制以下命令到终端执行

为确保你提交的代码身份被 Gitee 正确识别,请执行以下命令完成配置

git config --global user.name userName 
git config --global user.email userEmail

初次使用 SSH 协议进行代码克隆、推送等操作时,需按下述提示完成 SSH 配置

1 生成 RSA 密钥

2 获取 RSA 公钥内容,并配置到 SSH公钥中

在 Gitee 上使用 SVN,请访问使用指南

使用 HTTPS 协议时,命令行会出现如下账号密码验证步骤。基于安全考虑,Gitee 建议配置并使用私人令牌替代登录密码进行克隆、推送等操作

Username for 'https://gitee.com': userName

Password for 'https://userName@gitee.com': # 私人令牌

新建文件新建 Diagram 文件

新建子模块

上传文件

分支 68

标签 88

贡献代码

同步代码

创建 Pull Request

了解更多

对比差异通过 Pull Request 同步

同步更新到分支

通过 Pull Request 同步

将会在向当前分支创建一个 Pull
Request,合入后将完成同步

Dominik Charousset Prefer CAF's own print over snprintf b0ec89e

7319 次提交

.ci

.github/workflows

cmake

doc

examples

libcaf_io

manual

robot

scripts

tools

.cirrus.yml

.clang-format

.clang-tidy

.cppcheck-suppressions

.gitignore

.gitmodules

.typos-config.toml

CHANGELOG.md

CMakeLists.txt

CONTRIBUTING.md

Doxyfile

LICENSE

README.md

configure

README

BSD-3-Clause

# CAF: the C++ Actor Framework

CAF is an open source implementation of the actor model for C++ featuring
lightweight & fast actor implementations, pattern matching for messages, network
transparent messaging, and more.

[![Gitter][gitter-badge]](https://gitter.im/actor-framework/chat)
[![Documentation Status][docs-badge]](http://actor-framework.readthedocs.io/en/latest/?badge=latest)

## Online Resources

* __Homepage__: https://www.actor-framework.org
* __Developer Blog__: https://www.actor-framework.org/blog
* __Guides and Tutorials__: https://www.cafcademy.com/articles
* __Manual__: https://actor-framework.readthedocs.io
* __Doxygen__: https://www.actor-framework.org/doxygen/

## Report Bugs / Get Help

* __Open Issues on GitHub__: https://github.com/actor-framework/actor-framework/issues/new
* __Ask Questions on StackOverflow__: https://stackoverflow.com/questions/ask?tags=c%2b%2b-actor-framework

## Community

* __Chat__: https://gitter.im/actor-framework/chat
* __Twitter__: https://twitter.com/actor_framework
* __User Mailing List__: https://groups.google.com/d/forum/actor-framework

## Get CAF

We do not officially maintain packages for CAF. However, some of our community
members made packages available for these package managers:

- [Conan](https://conan.io/center/caf)
- [FreeBSD Ports](https://svnweb.freebsd.org/ports/head/devel/caf)
- [Homebrew](https://formulae.brew.sh/formula/caf).
- [VCPKG](https://github.com/microsoft/vcpkg/tree/master/ports/caf)

## Get the Sources

```sh
git clone https://github.com/actor-framework/actor-framework.git
cd actor-framework
```

## Build CAF from Source

CAF uses [CMake](http://www.cmake.org) as its build system of choice. To make
building CAF more convenient from the command line, we provide a `configure`
script that wraps the CMake invocation. The script only works on UNIX systems.
On Windows, we recommend generating an MSVC project file via CMake for native
builds.

### Using the `configure` Script

The script is a convenient frontend for `CMake`. See `configure -h` for a list
of available options. By default, the script creates a `build` directory and
asks CMake to generate a `Makefile`. A build with default settings generally
follows these steps:

```sh
./configure
cd build
make
make test [optional]
make install [as root, optional]
```

### Using CMake

To generate a Makefile for building CAF with default settings, either use a
CMake GUI or perform these steps on the command line:

```sh
mkdir build
cd build
cmake ..
```

After this step, `cmake -LH` prints the most useful configuration options for
CAF, their default value, and a helptext.

Other CMake projects can add CAF as a dependency by using `find_package` and
listing the required modules (e.g., `core` or `io`) . When installing CAF to a
non-standard location, set `CAF_ROOT` prior to calling `find_package`.

## Dependencies

* CMake (for building CAF)
* OpenSSL (only when building the OpenSSL module)

## Supported Platforms

C++ is an evolving language. Compiler vendors constantly add more language and
standard library features. Since CAF runs on many platforms, this means we need
a policy that on the one hand ensures that we only use a widely supported subset
of C++ and on the other hand that we naturally progress with the shifting
landscape to eventually catch up to more recent C++ additions (in order to not
"get stuck").

So instead of singling out individual compiler versions, we build CAF for each
commit on all platforms that we currently deem relevant. Everything that passes
our CI is "fair game".

Our CI covers Windows (latest MSVC release), macOS (latest Xcode release),
FreeBSD (latest) and several Linux distributions (via the Docker images found
[here](https://github.com/actor-framework/actor-framework/tree/master/.ci)). For
Linux, we aim to support the current releases (that still receive active
support) for the major distributions. Note that we do not build on Linux
distributions with rolling releases, because they generally provide more recent
build tools than distributions with traditional release schedules and thus would
only add redundancy.

## Build Documentation Locally

- Building an offline version of the manual requires
 [Sphinx](https://www.sphinx-doc.org):
 ```sh
 cd manual
 sphinx-build . html
 ```
- Building an offline version of the API reference documentation requires
 [Doxygen](http://www.doxygen.nl) (simply run the `doxygen` command at the
 root directory of the repository).

## Scientific Use

If you use CAF in a scientific context, please use one of the following citations:

```bibtex
@inproceedings{cshw-nassp-13,
 author = {Dominik Charousset and Thomas C. Schmidt and Raphael Hiesgen and Matthias W{\"a}hlisch},
 title = {{Native Actors -- A Scalable Software Platform for Distributed, Heterogeneous Environments}},
 booktitle = {Proc. of the 4rd ACM SIGPLAN Conference on Systems, Programming, and Applications (SPLASH '13), Workshop AGERE!},
 pages = {87--96},
 month = {Oct.},
 year = {2013},
 publisher = {ACM},
 address = {New York, NY, USA}
}

@article{chs-rapc-16,
 author = {Dominik Charousset and Raphael Hiesgen and Thomas C. Schmidt},
 title = {{Revisiting Actor Programming in C++}},
 journal = {Computer Languages, Systems \& Structures},
 volume = {45},
 year = {2016},
 month = {April},
 pages = {105--131},
 publisher = {Elsevier}
}
```

You can find the papers online at http://dx.doi.org/10.1145/2541329.2541336 and
http://dx.doi.org/10.1016/j.cl.201601002.

[docs-badge]: https://readthedocs.org/projects/actor-framework/badge/?version=latest

[gitter-badge]: https://img.shields.io/badge/gitter-join%20chat%20%E2%86%92-brightgreen.svg

Copyright (c) 2011-2021, Dominik Charousset All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.