From 84463e5388229ba58130f05f29ee8f5515727bb2 Mon Sep 17 00:00:00 2001 From: Christoph Thiede Date: Mon, 9 Oct 2023 20:05:28 +0200 Subject: [PATCH] ...resolve todo... --- docs/paper/sections/05_use_case.tex | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/paper/sections/05_use_case.tex b/docs/paper/sections/05_use_case.tex index 1447be3..4241770 100644 --- a/docs/paper/sections/05_use_case.tex +++ b/docs/paper/sections/05_use_case.tex @@ -37,5 +37,3 @@ \section{Use Case: Exploring the Internals of a Regular Expression Engine} Besides, she also could notice that almost 50\si{\percent} of the time was spent in the match optimizer. Without a closer idea of the role of this object, she might suspect this step to be a bottleneck in the construction and wonder if the optimization is optional and could be skipped for certain uses of the regular expression. To dive deeper into the implementation of the \code{Regex} package, she can expand the flame graph of the timeline, identify a few entry point methods of the objects that she finds most interesting (e.g., \code{RxParser>>parseStream:}), and open them in the Squeak IDE to browse their source code. - -% TODO: maybe provide link to video of the trace?