Question: There is a string: "python php ruby javascript jsonp perhapsphpisoutdated"
For this string, use pure regular expression to get all words with p but not ph
Output array [ 'python', 'javascript', 'jsonp' ]
I have been thinking about this problem for a long time and I have no idea
My solution is
<code>var result = str.match(/\b\w*(?=p)\w*\b/g) .filter((value)=>!/.*(?=ph)/.test(value)) var result2 = str.match( /\b((?!ph|\s).)*((p[^h\s]((?!ph|\s).)*)|p)\b/g ) console.log(result2)</code>
But it does not meet the requirements of pure regularity
A big guy in the group gave this answer
<code>/\b((?!ph|\s).)*((p[^h\s]((?!ph|\s).)*)|p)\b/g </code>
Works perfectly
But I can’t understand it, I hope someone can help me understand it
Reply content:
Question: There is a string: "python php ruby javascript jsonp perhapsphpisoutdated"
For this string, use pure regular expression to get all words with p but not ph
Output array [ 'python', 'javascript', 'jsonp' ]
I have been thinking about this problem for a long time and I have no idea
My solution is
<code>var result = str.match(/\b\w*(?=p)\w*\b/g) .filter((value)=>!/.*(?=ph)/.test(value)) var result2 = str.match( /\b((?!ph|\s).)*((p[^h\s]((?!ph|\s).)*)|p)\b/g ) console.log(result2)</code>
But it does not meet the requirements of pure regularity
A big guy in the group gave this answer
<code>/\b((?!ph|\s).)*((p[^h\s]((?!ph|\s).)*)|p)\b/g </code>
Works perfectly
But I can’t understand it, I hope someone can help me understand it
<code>var str = 'python php ruby javascript jsonp perhapsphpisoutdated'; var reg = /\b(\w*(p[^h\s](?!ph))\w*)\b/g; str.match(reg); // => ["python", "javascript", "perhapsphpisoutdated"]</code>
b
is the boundary character, and the range is the characters betweenw
andW
.
()
identifies a subexpression.
(?!)
identifies a reverse lookahead assertion. Unlike subexpressions, lookahead assertions will not be recorded.
[^]
identifies the set that does not meet the conditions
So the above regular meaning is Get the string between the boundaries that contains "p" but the string immediately following it is not "h" or "space", and it does not contain "ph" either
b((?!ph|s).)*((p[^hs]((?!ph|s).)*)|p)b/g
b
is a boundary character
So the corresponding match for each word is:((?!ph|s).)*((p[^hs]((?!ph|s).)*)|p)
Split this expression into three parts:
((?!ph|s).)*
(p[^hs]((?!ph|s).)*)
p
The most common expression is ((?!ph|s).)*
Let’s analyze it
"The Definitive Guide to JavaScript" says:
(?!p)
is a zero-width negative lookahead assertion, which means that the following characters do not matchp
The zero width here means that it does not occupy the matching :
This may be difficult to understand, for example:
Calculate the value of
"1234".match(/((?!34).)*/)
For the first time
(?!34)
there is nothing before, ignore it, only match.
, match"1"
, the remaining string"234"
Match
"234"
and test whether"23"
matches?!
in"34"
, the result does not match, continue,"23"
is not consumed, next.
matched"2"
,matches
"34"
, because"34"
matches?!
in"34"
, the matching is terminated
The matching result of the entire expression is "12"
Conclusion: The string matched by the expression in the form of
/((?!p).)*/
is the part beforep
Let’s look at the previous three expressions here:
((?!ph|s).)*
(p[^hs]((?!ph|s).)*)
p
The first expression means matching the longest possible characters before
"ph"
or spaces in the wordThe second expression matches the characters
"p"
and after in the word. It is required that the first character after"p"
cannot be"h"
, and it is also required not to match"ph"
The third expression matches a single
"p"
character, because the shortest matching form in the previous match isp[^hs]
, which is at least two characters, and a single "p" character poster Required but not included, so matched individually
After sorting it out, you will find that none of the three matching expressions above match "ph"
, but there must be "p"
among them, which fully meets the requirements of the topic

ThesecrettokeepingaPHP-poweredwebsiterunningsmoothlyunderheavyloadinvolvesseveralkeystrategies:1)ImplementopcodecachingwithOPcachetoreducescriptexecutiontime,2)UsedatabasequerycachingwithRedistolessendatabaseload,3)LeverageCDNslikeCloudflareforservin

You should care about DependencyInjection(DI) because it makes your code clearer and easier to maintain. 1) DI makes it more modular by decoupling classes, 2) improves the convenience of testing and code flexibility, 3) Use DI containers to manage complex dependencies, but pay attention to performance impact and circular dependencies, 4) The best practice is to rely on abstract interfaces to achieve loose coupling.

Yes,optimizingaPHPapplicationispossibleandessential.1)ImplementcachingusingAPCutoreducedatabaseload.2)Optimizedatabaseswithindexing,efficientqueries,andconnectionpooling.3)Enhancecodewithbuilt-infunctions,avoidingglobalvariables,andusingopcodecaching

ThekeystrategiestosignificantlyboostPHPapplicationperformanceare:1)UseopcodecachinglikeOPcachetoreduceexecutiontime,2)Optimizedatabaseinteractionswithpreparedstatementsandproperindexing,3)ConfigurewebserverslikeNginxwithPHP-FPMforbetterperformance,4)

APHPDependencyInjectionContainerisatoolthatmanagesclassdependencies,enhancingcodemodularity,testability,andmaintainability.Itactsasacentralhubforcreatingandinjectingdependencies,thusreducingtightcouplingandeasingunittesting.

Select DependencyInjection (DI) for large applications, ServiceLocator is suitable for small projects or prototypes. 1) DI improves the testability and modularity of the code through constructor injection. 2) ServiceLocator obtains services through center registration, which is convenient but may lead to an increase in code coupling.

PHPapplicationscanbeoptimizedforspeedandefficiencyby:1)enablingopcacheinphp.ini,2)usingpreparedstatementswithPDOfordatabasequeries,3)replacingloopswitharray_filterandarray_mapfordataprocessing,4)configuringNginxasareverseproxy,5)implementingcachingwi

PHPemailvalidationinvolvesthreesteps:1)Formatvalidationusingregularexpressionstochecktheemailformat;2)DNSvalidationtoensurethedomainhasavalidMXrecord;3)SMTPvalidation,themostthoroughmethod,whichchecksifthemailboxexistsbyconnectingtotheSMTPserver.Impl


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 Linux new version
SublimeText3 Linux latest version

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Notepad++7.3.1
Easy-to-use and free code editor
