From 87c8a5e8955a57e6365adb4aa64575308b17c47d Mon Sep 17 00:00:00 2001 From: Aki Date: Fri, 19 Jul 2024 23:55:23 +0200 Subject: Use multiset-like data structure for storing headers This looks like an overkill because it is one. The space and time complexity of the multiset structure is rather bad. At this point it stays mostly because of sunk cost fallacy. It will provide OK abstraction layer to build the rest of this forsaken project. --- headers.lua | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'headers.lua') diff --git a/headers.lua b/headers.lua index 972b360..8726615 100755 --- a/headers.lua +++ b/headers.lua @@ -5,13 +5,13 @@ Prints list of headers from a standard or available standards (optional string) Standard to display headers for ]] local dir = require "pl.dir" -local parse = require "headers.parser" +local parser = require "headers.parser".new() local definitions = dir.getfiles(args.d, "*.lua") for _, filename in pairs(definitions) do local handle = io.open(filename) local data = handle:read("a") handle:close() - if parse(data, args.selection) then + if parser:parse(data, args.selection) then return -- interface is yet to be properly defined, this allows only for first-result queries end end -- cgit v1.1