mirror of
https://github.com/VectorCamp/vectorscan.git
synced 2025-06-28 16:41:01 +03:00
Update compilation.rst
fixed two spelling mistakes
This commit is contained in:
parent
3ca3602755
commit
7b406c647c
@ -75,12 +75,12 @@ characters exist in regular grammer like ``[``, ``]``, ``(``, ``)``, ``{``,
|
|||||||
While in pure literal case, all these meta characters lost extra meanings
|
While in pure literal case, all these meta characters lost extra meanings
|
||||||
expect for that they are just common ASCII codes.
|
expect for that they are just common ASCII codes.
|
||||||
|
|
||||||
Hyperscan is initially designed to process common regualr expressions. It is
|
Hyperscan is initially designed to process common regular expressions. It is
|
||||||
hence embedded with a complex parser to do comprehensive regular grammer
|
hence embedded with a complex parser to do comprehensive regular grammer
|
||||||
interpretion. Particularly, the identification of above meta characters is the
|
interpretion. Particularly, the identification of above meta characters is the
|
||||||
basic step for the interpretion of far more complex regular grammers.
|
basic step for the interpretion of far more complex regular grammers.
|
||||||
|
|
||||||
However in real cases, patterns may not always be regualr expressions. They
|
However in real cases, patterns may not always be regular expressions. They
|
||||||
could just be pure literals. Problem will come if the pure literals contain
|
could just be pure literals. Problem will come if the pure literals contain
|
||||||
regular meta characters. Supposing fed directly into traditional Hyperscan
|
regular meta characters. Supposing fed directly into traditional Hyperscan
|
||||||
compile API, all these meta characters will be interpreted in predefined ways,
|
compile API, all these meta characters will be interpreted in predefined ways,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user