392[Medium]: Is Subsequence

本文介绍了一个经典的字符串匹配问题——检查一个字符串是否为另一个字符串的子序列,并提供了一种使用双循环进行暴力匹配的方法。该方法适用于短字符串s与长字符串t的匹配场景。

Part1:问题描述

Given a string s and a string t, check if s is subsequence of t.

You may assume that there is only lower case English letters in both s and tt is potentially a very long (length ~= 500,000) string, and sis a short string (<=100).

A subsequence of a string is a new string which is formed from the original string by deleting some (can be none) of the characters without disturbing the relative positions of the remaining characters. (ie, "ace" is a subsequence of "abcde" while "aec" is not).

Example 1:
s = "abc"t = "ahbgdc"

Return true.

Example 2:
s = "axc"t = "ahbgdc"

Return false.

Follow up:
If there are lots of incoming S, say S1, S2, ... , Sk where k >= 1B, and you want to check one by one to see if T has its subsequence. In this scenario, how would you change your code?

Credits:
Special thanks to @pbrother for adding this problem and creating all test cases.



Part2:解题思路

  这一题我用的暴力解题,直接2个for循环判断s里的字符有没有在t中出现,值得注意的是字符出现的顺序也要一致。我觉得我有改进的地方在于第二个for循环的时候我用的下标是一个函数里面的全局变量index,这样就可以保证下一次从t中开始找的字符是上一次判断用过的字符之后的。第一个if里面有嵌套的一个if是因为不加类似第一个样例--最后一个相等的字符在最后出现时的样例判断会出错。


Part3:代码

class Solution {
public:
    bool isSubsequence(string s, string t) {
	int length1 = s.length();
	int length2 = t.length();
	if (length1 > length2) return false;
	int index = 0;
	int i = 0;
	for (i; i < length1; i++) {
		for (index; index < length2; ) {
			if (s[i] == t[index++]) {
				if (index == length2 && i != length1 - 1) {
					return false;
				}
				break;
			}
			
			if (index == length2) {
				return false;
			}
		}
	}
	return true;
}
};


CVE-2022-41741 A vulnerability in the module ngx_http_mp4_module might allow a local attacker to corrupt NGINX worker memory, resulting in its termination or potential other impact using a specially crafted audio or video file. The attack is only possible if an attacker can gain privileged access to the host running NGINX, place a specially crafted audio or video file within the webroot, and then trigger NGINX to process the specially crafted file. v3.1 v4.0 Base 7.0 7.3 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CVSS v4 Score: Base 7.3 Metric Value Comments Attack Vector Local An attacker must be able to access the vulnerable system with a local, interactive session. Attack Complexity Low No specialized conditions or advanced knowledge are required. Attack Requirements Present Multiple conditions that require target specific reconnaissance and preparation must be satisfied in order to achieve successful exploitation of this vulnerability. Privileges Required Low An attacker must be able to place a file within the web root to be processed by NGINX. User Interaction None No user interaction is required for an attacker to successfully exploit the vulnerability. Vulnerable System Confidentiality High The attacker could execute arbitrary code on the vulnerable system with elevated privileges. Vulnerable System Integrity High The attacker could execute arbitrary code on the vulnerable system with elevated privileges. Vulnerable System Availability High The attacker could execute arbitrary code on the vulnerable system with elevated privileges. Subsequent System Confidentiality None There is no impact to the subsequent system confidentiality. Subsequent System Integrity None There is no impact to the subsequent system integrity. Subsequent System Availability None There is no impact to the subsequent system availability. CVE-2020-3549 A vulnerability in the sftunnel functionality of Cisco Firepower Management Center (FMC) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to obtain the device registration hash. The vulnerability is due to insufficient sftunnel negotiation protection during initial device registration. An attacker in a man-in-the-middle position could exploit this vulnerability by intercepting a specific flow of the sftunnel communication between an FMC device and an FTD device. A successful exploit could allow the attacker to decrypt and modify the sftunnel communication between FMC and FTD devices, allowing the attacker to modify configuration data sent from an FMC device to an FTD device or alert data sent from an FTD device to an FMC device. v3.1 v4.0 Base 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H 7.7 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Base + Threat 5.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U CVSS v4 Score: Base + Threat 5.2 Metric Value Comments Attack Vector Network The vulnerable system is accessible from remote networks. Attack Complexity Low No specialized conditions or advanced knowledge are required. Attack Requirements Present An attacker must be on-path to be able to intercept communications between affected systems. Privileges Required None No privileges are required for an attacker to successfully exploit the vulnerability. User Interaction Passive A user must be logged in and using the application for traffic to be generated that an attacker could capture. Vulnerable System Confidentiality High An attacker could gain access to the system with a highly privileged user account. Vulnerable System Integrity High An attacker could gain access to the system with a highly privileged user account. Vulnerable System Availability High An attacker could gain access to the system with a highly privileged user account. Subsequent System Confidentiality None There is no impact to the vulnerable system confidentiality. Subsequent System Integrity None There is no impact to the vulnerable system integrity. Subsequent System Availability None There is no impact to the vulnerable system availability. Exploit Maturity Unreported There is no known proof-of-concept code or malicious exploitation of this vulnerability.
07-09
代码下载地址: https://pan.quark.cn/s/b4a8e0160cfc 齿轮与轴系零件在机械设备中扮演着至关重要的角色,它们负责实现动力传输、调整运动形态以及承受工作载荷等核心功能。 在机械工程的设计实践中,齿轮和轴系的设计是一项关键的技术任务,其内容涵盖了材料选用、构造规划、承载能力分析等多个技术层面。 下面将系统性地介绍《齿轮及轴系零件结构设计指导书》中的核心知识点。 一、齿轮设计1. 齿轮种类:依据齿廓轮廓的不同,齿轮可划分为直齿齿轮、斜齿轮以及人字齿轮等类别,各类齿轮均具有特定的性能特点与适用工况,能够满足多样化的工作环境与载荷需求。 2. 齿轮规格参数:模数大小、压力角数值、齿数数量、分度圆尺寸等是齿轮设计的基础数据,这些参数直接决定了齿轮的物理尺寸与运行性能。 3. 齿轮材质选用:齿轮材料的确定需综合评估其耐磨损性能、硬度水平以及韧性表现,常用的材料包括铸铁、钢材、铝合金等。 4. 齿轮强度验证:需进行齿面接触应力分析与齿根弯曲应力分析,以确保齿轮在实际运行过程中不会出现过度磨损或结构破坏。 5. 齿轮加工工艺:涉及切削加工、滚齿加工、剃齿加工、淬火处理等工艺流程,工艺方案的选择将直接影响齿轮的加工精度与使用寿命。 二、轴设计1. 轴的分类方式:依据轴在机械装置中的功能定位与受力特点,可将轴划分为心轴、转轴以及传动轴等类型。 2. 轴的材料选择:通常采用钢材作为轴的材料,例如碳素结构钢或合金结构钢,特殊需求时可选用不锈钢材料或轻质合金材料。 3. 轴的构造规划:需详细考虑轴的轴向长度、截面直径、键槽布置、轴承安装位置等要素,以满足轴的强度要求、刚度要求以及稳定性要求。 4. 轴的强度验证:需进行轴的扭转强度分析与弯曲强度分析,以防止轴在运行过程中发生塑性变形...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值