Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 13356] config_query gets slower as CONFIGURE progresses

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 13356] config_query gets slower as CONFIGURE progresses
  • Date: 14 Jan 2007 04:00:29 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=13356





------- Additional Comments From acedit AT armory.com 2007-01-13 22:00 -------
I prefer to err on the side of safety. There have been cases where mis-used
*'s
expanded to directory listings. It might not currently be possible in [[ ]]'s.

In either the glob matching case or the exact matching case the entire
variable
must be inspected. So both implementations run in time linear to the length of
the variable. Neither should be significantly different in performance than
the
other. I haven't seen any numbers, so I dont understand why you've jumped to
the
conclusion that the iterative version is slower than the glob matching one.

I think the exact matching case is actually clearer than the glob matching
case.
The glob version you have to notice the carefully places *'s. The other one is
more akin to "traditional" data structures.

Furthermore, its easier to prove the exact matching case is "correct". In the
glob matching version the user can throw in their own patterns, or more
likely,
have to backquote their patterns to avoid false matches. In reality no one
will
do that, as a result that would open things up to many potential bugs. Exact
matching avoids that issue.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page