Language APIs SDKs-C++-Exporters

2024-04-19 18:36
文章标签 c++ apis language exporters sdks

本文主要是介绍Language APIs SDKs-C++-Exporters，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

Exporters

导出器

Send telemetry to the OpenTelemetry Collector to make sure it’s exported correctly. Using the Collector in production environments is a best practice. To visualize your telemetry, export it to a backend such as Jaeger , Zipkin , Prometheus , or a vendor-specific backend.
将遥测数据发送到OpenTelemetry Collector以确保其导出正确。在生产环境中使用收集器是最佳实践。要可视化您的遥测数据，请将其导出到后端，例如 Jaeger、Zipkin、 Prometheus或特定于供应商的后端。

Available exporters

可用的导出器

The registry contains a list of exporters for C++.
注册表包含C++的导出器列表。

Among exporters, OpenTelemetry Protocol (OTLP) exporters are designed with the OpenTelemetry data model in mind, emitting OTel data without any loss of information. Furthermore, many tools that operate on telemetry data support OTLP (such as Prometheus , Jaeger, and most vendors), providing you with a high degree of flexibility when you need it. To learn more about OTLP, see OTLP Specification.
在导出器中，OpenTelemetry Protocol (OTLP)导出器在设计时考虑了 OpenTelemetry 数据模型，可在不丢失任何信息的情况下发出OTel数据。此外，许多对遥测数据进行操作的工具都支持OTLP（例如Prometheus、Jaeger和大多数供应商），在您需要时为您提供高度的灵活性。要了解有关OTLP的更多信息，请参阅OTLP规范。

This page covers the main OpenTelemetry C++ exporters and how to set them up.
本页介绍了主要的 OpenTelemetry C++ 导出器以及如何设置它们。

OTLP

Collector Setup

收集器设置

Note
笔记
If you have a OTLP collector or backend already set up, you can skip this section and setup the OTLP exporter dependencies for your application.
如果您已经设置了OTLP收集器或后端，则可以跳过本节并为您的应用程序设置OTLP导出器依赖项。

To try out and verify your OTLP exporters, you can run the collector in a docker container that writes telemetry directly to the console.
要尝试和验证OTLP导出器，您可以在Docker容器中运行收集器，将遥测数据直接写入控制台。

In an empty directory, create a file called collector-config.yaml with the following content:
在空目录中，创建一个包含collector-config.yaml以下内容的文件：

receivers:otlp:protocols:grpc:endpoint: 0.0.0.0:4317http:endpoint: 0.0.0.0:4318
exporters:debug:verbosity: detailed
service:pipelines:traces:receivers: [otlp]exporters: [debug]metrics:receivers: [otlp]exporters: [debug]logs:receivers: [otlp]exporters: [debug]

Now run the collector in a docker container:
现在在 Docker 容器中运行收集器：

docker run -p 4317:4317 -p 4318:4318 --rm -v $(pwd)/collector-config.yaml:/etc/otelcol/config.yaml otel/opentelemetry-collector

This collector is now able to accept telemetry via OTLP. Later you may want to configure the collector to send your telemetry to your observability backend.
该收集器现在能够通过OTLP接受遥测数据。稍后您可能需要配置收集器以将遥测数据发送到可观测性后端。

Dependencies

If you want to send telemetry data to an OTLP endpoint (like the OpenTelemetry Collector, Jaeger or Prometheus), you can choose between two different protocols to transport your data:
如果您想将遥测数据发送到OTLP端点（例如 OpenTelemetry Collector、Jaeger或 Prometheus），您可以选择两种不同的协议来传输数据：

  • HTTP/protobuf
  • gRPC

Make sure that you have set the right cmake build variables while building OpenTelemetry C++ from source :
确保在从源代码构建OpenTelemetry C++时设置了正确的cmake构建变量：

  • -DWITH_OTLP_GRPC=ON: To enable building OTLP gRPC exporter.
    启用构建 OTLP gRPC 导出器。
  • -DWITH_OTLP_HTTP=ON: To enable building OTLP HTTP exporter.
    启用构建 OTLP HTTP 导出器。

Usage

用法

Next, configure the exporter to point at an OTLP endpoint in your code.
接下来，将导出器配置为指向代码中的 OTLP 端点

// HTTP/proto
#include "opentelemetry/exporters/otlp/otlp_http_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_http_exporter_options.h"
#include "opentelemetry/sdk/trace/processor.h"
#include "opentelemetry/sdk/trace/batch_span_processor_factory.h"
#include "opentelemetry/sdk/trace/batch_span_processor_options.h"
#include "opentelemetry/sdk/trace/tracer_provider_factory.h"
#include "opentelemetry/trace/provider.h"
#include "opentelemetry/sdk/trace/tracer_provider.h"#include "opentelemetry/exporters/otlp/otlp_http_metric_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_http_metric_exporter_options.h"
#include "opentelemetry/metrics/provider.h"
#include "opentelemetry/sdk/metrics/aggregation/default_aggregation.h"
#include "opentelemetry/sdk/metrics/export/periodic_exporting_metric_reader.h"
#include "opentelemetry/sdk/metrics/export/periodic_exporting_metric_reader_factory.h"
#include "opentelemetry/sdk/metrics/meter_context_factory.h"
#include "opentelemetry/sdk/metrics/meter_provider.h"
#include "opentelemetry/sdk/metrics/meter_provider_factory.h"#include "opentelemetry/exporters/otlp/otlp_http_log_record_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_http_log_record_exporter_options.h"
#include "opentelemetry/logs/provider.h"
#include "opentelemetry/sdk/logs/logger_provider_factory.h"
#include "opentelemetry/sdk/logs/processor.h"
#include "opentelemetry/sdk/logs/simple_log_record_processor_factory.h"namespace trace_api = opentelemetry::trace;
namespace trace_sdk = opentelemetry::sdk::trace;namespace metric_sdk = opentelemetry::sdk::metrics;
namespace metrics_api = opentelemetry::metrics;namespace otlp = opentelemetry::exporter::otlp;namespace logs_api = opentelemetry::logs;
namespace logs_sdk = opentelemetry::sdk::logs;void InitTracer()
{trace_sdk::BatchSpanProcessorOptions bspOpts{};otlp::OtlpHttpExporterOptions opts;opts.url = "http://localhost:4318/v1/traces";auto exporter  = otlp::OtlpHttpExporterFactory::Create(opts);auto processor = trace_sdk::BatchSpanProcessorFactory::Create(std::move(exporter), bspOpts);std::shared_ptr<trace_api::TracerProvider> provider =  trace_sdk::TracerProviderFactory::Create(std::move(processor));trace_api::Provider::SetTracerProvider(provider);
}void InitMetrics()
{otlp::OtlpHttpMetricExporterOptions opts;opts.url = "http://localhost:4318/v1/metrics";auto exporter = otlp::OtlpHttpMetricExporterFactory::Create(opts);metric_sdk::PeriodicExportingMetricReaderOptions reader_options;reader_options.export_interval_millis = std::chrono::milliseconds(1000);reader_options.export_timeout_millis  = std::chrono::milliseconds(500);auto reader = metric_sdk::PeriodicExportingMetricReaderFactory::Create(std::move(exporter), reader_options);auto context = metric_sdk::MeterContextFactory::Create();context->AddMetricReader(std::move(reader));auto u_provider = metric_sdk::MeterProviderFactory::Create(std::move(context));std::shared_ptr<metrics_api::MeterProvider> provider(std::move(u_provider));metrics_api::Provider::SetMeterProvider(provider);
}void InitLogger()
{otlp::OtlpHttpLogRecordExporterOptions opts;opts.url = "http://localhost:4318/v1/logs";auto exporter  = otlp::OtlpHttpLogRecordExporterFactory::Create(opts);auto processor = logs_sdk::SimpleLogRecordProcessorFactory::Create(std::move(exporter));std::shared_ptr<logs_api::LoggerProvider> provider =logs_sdk::LoggerProviderFactory::Create(std::move(processor));logs_api::Provider::SetLoggerProvider(provider);
}
// gRPC
#include "opentelemetry/exporters/otlp/otlp_grpc_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_grpc_exporter_options.h"
#include "opentelemetry/sdk/trace/processor.h"
#include "opentelemetry/sdk/trace/batch_span_processor_factory.h"
#include "opentelemetry/sdk/trace/batch_span_processor_options.h"
#include "opentelemetry/sdk/trace/tracer_provider_factory.h"
#include "opentelemetry/trace/provider.h"
#include "opentelemetry/sdk/trace/tracer_provider.h"#include "opentelemetry/exporters/otlp/otlp_grpc_metric_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_grpc_metric_exporter_options.h"
#include "opentelemetry/metrics/provider.h"
#include "opentelemetry/sdk/metrics/aggregation/default_aggregation.h"
#include "opentelemetry/sdk/metrics/export/periodic_exporting_metric_reader.h"
#include "opentelemetry/sdk/metrics/export/periodic_exporting_metric_reader_factory.h"
#include "opentelemetry/sdk/metrics/meter_context_factory.h"
#include "opentelemetry/sdk/metrics/meter_provider.h"
#include "opentelemetry/sdk/metrics/meter_provider_factory.h"#include "opentelemetry/exporters/otlp/otlp_grpc_log_record_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_grpc_log_record_exporter_options.h"
#include "opentelemetry/logs/provider.h"
#include "opentelemetry/sdk/logs/logger_provider_factory.h"
#include "opentelemetry/sdk/logs/processor.h"
#include "opentelemetry/sdk/logs/simple_log_record_processor_factory.h"namespace trace_api = opentelemetry::trace;
namespace trace_sdk = opentelemetry::sdk::trace;namespace metric_sdk = opentelemetry::sdk::metrics;
namespace metrics_api = opentelemetry::metrics;namespace otlp = opentelemetry::exporter::otlp;namespace logs_api = opentelemetry::logs;
namespace logs_sdk = opentelemetry::sdk::logs;void InitTracer()
{trace_sdk::BatchSpanProcessorOptions bspOpts{};opentelemetry::exporter::otlp::OtlpGrpcExporterOptions opts;opts.endpoint = "localhost:4317";opts.use_ssl_credentials = true;opts.ssl_credentials_cacert_as_string = "ssl-certificate";auto exporter  = otlp::OtlpGrpcExporterFactory::Create(opts);auto processor = trace_sdk::BatchSpanProcessorFactory::Create(std::move(exporter), bspOpts);std::shared_ptr<opentelemetry::trace_api::TracerProvider> provider =trace_sdk::TracerProviderFactory::Create(std::move(processor));// Set the global trace providertrace_api::Provider::SetTracerProvider(provider);
}void InitMetrics()
{otlp::OtlpGrpcMetricExporterOptions opts;opts.endpoint = "localhost:4317";opts.use_ssl_credentials = true;opts.ssl_credentials_cacert_as_string = "ssl-certificate";auto exporter = otlp::OtlpGrpcMetricExporterFactory::Create(opts);metric_sdk::PeriodicExportingMetricReaderOptions reader_options;reader_options.export_interval_millis = std::chrono::milliseconds(1000);reader_options.export_timeout_millis  = std::chrono::milliseconds(500);auto reader = metric_sdk::PeriodicExportingMetricReaderFactory::Create(std::move(exporter), reader_options);auto context = metric_sdk::MeterContextFactory::Create();context->AddMetricReader(std::move(reader));auto u_provider = metric_sdk::MeterProviderFactory::Create(std::move(context));std::shared_ptr<opentelemetry::metrics::MeterProvider> provider(std::move(u_provider));metrics_api::Provider::SetMeterProvider(provider);
}void InitLogger()
{otlp::OtlpGrpcLogRecordExporterOptions opts;opts.endpoint = "localhost:4317";opts.use_ssl_credentials = true;opts.ssl_credentials_cacert_as_string = "ssl-certificate";auto exporter  = otlp::OtlpGrpcLogRecordExporterFactory::Create(opts);auto processor = logs_sdk::SimpleLogRecordProcessorFactory::Create(std::move(exporter));nostd::shared_ptr<logs_api::LoggerProvider> provider(logs_sdk::LoggerProviderFactory::Create(std::move(processor)));logs_api::Provider::SetLoggerProvider(provider);
}

Console

To debug your instrumentation or see the values locally in development, you can use exporters writing telemetry data to the console (stdout).
要调试您的装置或在开发环境中查看本地值，您可以使用导出器将遥测数据写入控制台（stdout）。

While building OpenTelemetry C++ from source the OStreamSpanExporter is included in the build by default.
从源代码构建OpenTelemetry C++时， 默认情况下将其OStreamSpanExporter包含在构建中。

#include "opentelemetry/exporters/ostream/span_exporter_factory.h"
#include "opentelemetry/sdk/trace/exporter.h"
#include "opentelemetry/sdk/trace/processor.h"
#include "opentelemetry/sdk/trace/simple_processor_factory.h"
#include "opentelemetry/sdk/trace/tracer_provider_factory.h"
#include "opentelemetry/trace/provider.h"#include "opentelemetry/exporters/ostream/metrics_exporter_factory.h"
#include "opentelemetry/sdk/metrics/meter_provider.h"
#include "opentelemetry/sdk/metrics/meter_provider_factory.h"
#include "opentelemetry/metrics/provider.h"#include "opentelemetry/exporters/ostream/log_record_exporter_factory.h"
#include "opentelemetry/logs/provider.h"
#include "opentelemetry/sdk/logs/logger_provider_factory.h"
#include "opentelemetry/sdk/logs/processor.h"
#include "opentelemetry/sdk/logs/simple_log_record_processor_factory.h"namespace trace_api      = opentelemetry::trace;
namespace trace_sdk      = opentelemetry::sdk::trace;
namespace trace_exporter = opentelemetry::exporter::trace;namespace metrics_sdk      = opentelemetry::sdk::metrics;
namespace metrics_api      = opentelemetry::metrics;
namespace metrics_exporter = opentelemetry::exporter::metrics;namespace logs_api = opentelemetry::logs;
namespace logs_sdk = opentelemetry::sdk::logs;
namespace logs_exporter = opentelemetry::exporter::logs;void InitTracer()
{auto exporter  = trace_exporter::OStreamSpanExporterFactory::Create();auto processor = trace_sdk::SimpleSpanProcessorFactory::Create(std::move(exporter));std::shared_ptr<opentelemetry::trace::TracerProvider> provider = trace_sdk::TracerProviderFactory::Create(std::move(processor));trace_api::Provider::SetTracerProvider(provider);
}void InitMetrics()
{auto exporter = metrics_exporter::OStreamMetricExporterFactory::Create();auto u_provider = metrics_sdk::MeterProviderFactory::Create();std::shared_ptr<opentelemetry::metrics::MeterProvider> provider(std::move(u_provider));auto *p = static_cast<metrics_sdk::MeterProvider *>(u_provider.get());p->AddMetricReader(std::move(exporter));metrics_api::Provider::SetMeterProvider(provider);
}void InitLogger()
{auto exporter = logs_exporter::OStreamLogRecordExporterFactory::Create();auto processor = logs_sdk::SimpleLogRecordProcessorFactory::Create(std::move(exporter));nostd::shared_ptr<logs_api::LoggerProvider> provider(logs_sdk::LoggerProviderFactory::Create(std::move(processor)));logs_api::Provider::SetLoggerProvider(provider);
}

Jaeger

Jaeger natively supports OTLP to receive trace data. You can run Jaeger in a docker container with the UI accessible on port 16686 and OTLP enabled on ports 4317 and 4318:
Jaeger原生支持OTLP接收Trace数据。您可以在docker容器中运行Jaeger，并在端口16686上访问 UI，并在端口 4317和4318上启用 OTLP：

docker run --rm \-e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \-p 16686:16686 \-p 4317:4317 \-p 4318:4318 \-p 9411:9411 \jaegertracing/all-in-one:latest

Now following the instruction to setup the OTLP exporters.
现在按照说明设置OTLP导出器。

**

Prometheus

To send your metric data to Prometheus , you can either enable Prometheus’ OTLP Receiver and use the OTLP exporter or you can use the PrometheusHttpServer , a MetricReader, that starts an HTTP server that will collect metrics and serialize to Prometheus text format on request.
要将指标数据发送到Prometheus，您可以启用Prometheus的OTLP接收器并使用OTLP导出器，也可以使用PrometheusHttpServer——一个MetricReader来启动HTTP服务器，该服务器将收集指标并根据请求序列化为 Prometheus文本格式。

Backend Setup

后端设置

Note
笔记
If you have Prometheus or a Prometheus-compatible backend already set up, you can skip this section and setup the Prometheus or OTLP exporter dependencies for your application.
如果您已经设置了Prometheus或与Prometheus兼容的后端，则可以跳过本节并为您的应用程序设置Prometheus或OTLP导出器依赖项。

You can run Prometheus in a docker container, accessible on port 9090 by following these instructions:
您可以在Docker容器中运行Prometheus ，可以按照以下说明在9090端口上进行访问：

Create a file called prometheus.yml with the following content:
创建一个名为prometheus.yml的文件，内容如下：

scrape_configs:- job_name: dice-servicescrape_interval: 5sstatic_configs:- targets: [host.docker.internal:9464]

Run Prometheus in a docker container with the UI accessible on port 9090:
在 docker 容器中运行 Prometheus，并在端口9090上访问UI：

Note
笔记
When using Prometheus’ OTLP Receiver, make sure that you set the OTLP endpoint for metrics in your application to http://localhost:9090/api/v1/otlp.
使用 Prometheus 的 OTLP 接收器时，请确保将应用程序中指标的OTLP 端点设置为http://localhost:9090/api/v1/otlp。
Not all docker environments support host.docker.internal. In some cases you may need to replace host.docker.internal with localhost or the IP address of your machine.
并非所有docker环境都支持host.docker.internal。在某些情况下，您可能需要替换host.docker.internal为localhost或您计算机的IP地址。

Dependencies

依赖关系

To send your trace data to Prometheus , make sure that you have set the right cmake build variables while building OpenTelemetry C++ from source :
要将Trace数据发送到Prometheus ，请确保在从源代码构建 OpenTelemetry C++时设置了正确的 cmake 构建变量：

cmake -DWITH_PROMETHEUS=ON ...

Update your OpenTelemetry configuration to use the Prometheus Exporter:
更新您的 OpenTelemetry 配置以使用 Prometheus Exporter

#include "opentelemetry/exporters/prometheus/exporter_factory.h"
#include "opentelemetry/exporters/prometheus/exporter_options.h"
#include "opentelemetry/metrics/provider.h"
#include "opentelemetry/sdk/metrics/meter_provider.h"
#include "opentelemetry/sdk/metrics/meter_provider_factory.h"namespace metrics_sdk      = opentelemetry::sdk::metrics;
namespace metrics_api      = opentelemetry::metrics;
namespace metrics_exporter = opentelemetry::exporter::metrics;void InitMetrics()
{metrics_exporter::PrometheusExporterOptions opts;opts.url = "localhost:9464";auto prometheus_exporter = metrics_exporter::PrometheusExporterFactory::Create(opts);auto u_provider = metrics_sdk::MeterProviderFactory::Create();auto *p = static_cast<metrics_sdk::MeterProvider *>(u_provider.get());p->AddMetricReader(std::move(prometheus_exporter));std::shared_ptr<metrics_api::MeterProvider> provider(std::move(u_provider));metrics_api::Provider::SetMeterProvider(provider);
}

With the above you can access your metrics at http://localhost:9464/metrics . Prometheus or an OpenTelemetry Collector with the Prometheus receiver can scrape the metrics from this endpoint.
通过上述内容，您可以在http://localhost:9464/metrics访问您的指标。 Prometheus或带有Prometheus接收器的 OpenTelemetry Collector可以从此端点抓取指标。

Zipkin

Backend Setup

后端设置

Note
笔记
If you have Zipkin or a Zipkin-compatible backend already set up, you can skip this section and setup the Zipkin exporter dependencies for your application.
如果您已经设置了Zipkin或与Zipkin兼容的后端，则可以跳过本节并为您的应用程序设置Zipkin导出器依赖项 。

You can run Zipkin on in a Docker container by executing the following command:
您可以通过执行以下命令在Docker容器中运行Zipkin ：

docker run --rm -d -p 9411:9411 --name zipkin openzipkin/zipkin

Dependencies#

依赖关系

To send your trace data to Zipkin , make sure that you have set the right cmake build variables while building OpenTelemetry C++ from source :

cmake -DWITH_ZIPKIN=ON ...*

Update your OpenTelemetry configuration to use the Zipkin Exporter  and to send data to your Zipkin backend:
要将Trace数据发送到Zipkin ，请确保在从源代码构建OpenTelemetry C++时设置了正确的cmake构建变量 ：

#include "opentelemetry/exporters/zipkin/zipkin_exporter_factory.h"
#include "opentelemetry/sdk/resource/resource.h"
#include "opentelemetry/sdk/trace/processor.h"
#include "opentelemetry/sdk/trace/simple_processor_factory.h"
#include "opentelemetry/sdk/trace/tracer_provider_factory.h"
#include "opentelemetry/trace/provider.h"namespace trace     = opentelemetry::trace;
namespace trace_sdk = opentelemetry::sdk::trace;
namespace zipkin    = opentelemetry::exporter::zipkin;
namespace resource  = opentelemetry::sdk::resource;void InitTracer()
{zipkin::ZipkinExporterOptions opts;resource::ResourceAttributes attributes = {{"service.name", "zipkin_demo_service"}};auto resource                           = resource::Resource::Create(attributes);auto exporter                           = zipkin::ZipkinExporterFactory::Create(opts);auto processor = trace_sdk::SimpleSpanProcessorFactory::Create(std::move(exporter));std::shared_ptr<opentelemetry::trace::TracerProvider> provider =trace_sdk::TracerProviderFactory::Create(std::move(processor), resource);// Set the global trace providertrace::Provider::SetTracerProvider(provider);
}

Other available exporters

其他可用的导出器

There are many other exporters available. For a list of available exporters, see the registry.
还有许多其他导出器商可供选择。有关可用导出器商的列表，请参阅注册表。

Finally, you can also write your own exporter. For more information, see the SpanExporter Interface in the API documentation.
最后，您还可以编写自己的导出器。有关更多信息，请参阅 API 文档中的 SpanExporter 接口。

Batching span and log records

批处理跨度和日志记录

The OpenTelemetry SDK provides a set of default span and log record processors, that allow you to either emit spans one-by-on (“simple”) or batched. Using batching is recommended, but if you do not want to batch your spans or log records, you can use a simple processor instead as follows:
OpenTelemetry SDK 提供了一组默认的Span和日志记录处理器，允许您逐个（“简单”）或批量发出Span。建议使用批处理，但如果您不想对Span或日志记录进行批处理，则可以使用简单的处理器，如下所示：

// Bash
#include "opentelemetry/exporters/otlp/otlp_http_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_http_exporter_options.h"
#include "opentelemetry/sdk/trace/processor.h"
#include "opentelemetry/sdk/trace/batch_span_processor_factory.h"
#include "opentelemetry/sdk/trace/batch_span_processor_options.h"opentelemetry::sdk::trace::BatchSpanProcessorOptions options{};auto exporter  = opentelemetry::exporter::otlp::OtlpHttpExporterFactory::Create(opts);
auto processor = opentelemetry::sdk::trace::BatchSpanProcessorFactory::Create(std::move(exporter), options);

// Simple
#include "opentelemetry/exporters/otlp/otlp_http_exporter_factory.h"
#include "opentelemetry/exporters/otlp/otlp_http_exporter_options.h"
#include "opentelemetry/sdk/trace/processor.h"
#include "opentelemetry/sdk/trace/simple_processor_factory.h"auto exporter  = opentelemetry::exporter::otlp::OtlpHttpExporterFactory::Create(opts);
auto processor = opentelemetry::sdk::trace::SimpleSpanProcessorFactory::Create(std::move(exporter));

这篇关于Language APIs SDKs-C++-Exporters的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！


http://www.chinasem.cn/article/918282。

相关文章

Win32下C++实现快速获取硬盘分区信息

Win32下C++实现快速获取硬盘分区信息

《Win32下C++实现快速获取硬盘分区信息》这篇文章主要为大家详细介绍了Win32下C++如何实现快速获取硬盘分区信息,文中的示例代码讲解详细,感兴趣的小伙伴可以跟随小编一起学习一下... 实现代码CDiskDriveUtils.h#pragma once #include <wtypesbase
阅读更多...
C++ Primer 标准库vector示例详解

C++ Primer 标准库vector示例详解

《C++Primer标准库vector示例详解》该文章主要介绍了C++标准库中的vector类型,包括其定义、初始化、成员函数以及常见操作,文章详细解释了如何使用vector来存储和操作对象集合,... 目录3.3标准库Vector定义和初始化vector对象通列表初始化vector对象创建指定数量的元素值
阅读更多...
C++实现回文串判断的两种高效方法

C++实现回文串判断的两种高效方法

《C++实现回文串判断的两种高效方法》文章介绍了两种判断回文串的方法：解法一通过创建新字符串来处理,解法二在原字符串上直接筛选判断,两种方法都使用了双指针法,文中通过代码示例讲解的非常详细,需要的朋友... 目录一、问题描述示例二、解法一：将字母数字连接到新的 string思路代码实现代码解释复杂度分析三、
阅读更多...
C++一个数组赋值给另一个数组方式

C++一个数组赋值给另一个数组方式

《C++一个数组赋值给另一个数组方式》文章介绍了三种在C++中将一个数组赋值给另一个数组的方法：使用循环逐个元素赋值、使用标准库函数std::copy或std::memcpy以及使用标准库容器,每种方... 目录C++一个数组赋值给另一个数组循环遍历赋值使用标准库中的函数 std::copy 或 std::
阅读更多...
C++使用栈实现括号匹配的代码详解

C++使用栈实现括号匹配的代码详解

《C++使用栈实现括号匹配的代码详解》在编程中,括号匹配是一个常见问题,尤其是在处理数学表达式、编译器解析等任务时,栈是一种非常适合处理此类问题的数据结构,能够精确地管理括号的匹配问题,本文将通过C+... 目录引言问题描述代码讲解代码解析栈的状态表示测试总结引言在编程中，括号匹配是一个常见问题，尤其是在
阅读更多...
使用C++实现链表元素的反转

使用C++实现链表元素的反转

《使用C++实现链表元素的反转》反转链表是链表操作中一个经典的问题,也是面试中常见的考题,本文将从思路到实现一步步地讲解如何实现链表的反转,帮助初学者理解这一操作,我们将使用C++代码演示具体实现,同... 目录问题定义思路分析代码实现带头节点的链表代码讲解其他实现方式时间和空间复杂度分析总结问题定义给定
阅读更多...
C++初始化数组的几种常见方法(简单易懂)

C++初始化数组的几种常见方法(简单易懂)

《C++初始化数组的几种常见方法(简单易懂)》本文介绍了C++中数组的初始化方法,包括一维数组和二维数组的初始化,以及用new动态初始化数组,在C++11及以上版本中,还提供了使用std::array... 目录1、初始化一维数组1.1、使用列表初始化（推荐方式）1.2、初始化部分列表1.3、使用std::
阅读更多...
C++ Primer 多维数组的使用

C++ Primer 多维数组的使用

《C++Primer多维数组的使用》本文主要介绍了多维数组在C++语言中的定义、初始化、下标引用以及使用范围for语句处理多维数组的方法,具有一定的参考价值,感兴趣的可以了解一下... 目录多维数组多维数组的初始化多维数组的下标引用使用范围for语句处理多维数组指针和多维数组多维数组严格来说,C++语言没
阅读更多...
c++中std::placeholders的使用方法

c++中std::placeholders的使用方法

《c++中std::placeholders的使用方法》std::placeholders是C++标准库中的一个工具,用于在函数对象绑定时创建占位符,本文就来详细的介绍一下,具有一定的参考价值,感兴... 目录1. 基本概念2. 使用场景3. 示例示例 1：部分参数绑定示例 2：参数重排序4. 注意事项5.
阅读更多...
使用C++将处理后的信号保存为PNG和TIFF格式

使用C++将处理后的信号保存为PNG和TIFF格式

《使用C++将处理后的信号保存为PNG和TIFF格式》在信号处理领域,我们常常需要将处理结果以图像的形式保存下来,方便后续分析和展示,C++提供了多种库来处理图像数据,本文将介绍如何使用stb_ima... 目录1. PNG格式保存使用stb_imagephp_write库1.1 安装和包含库1.2 代码解
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2