Summary Files Commits Branches @commit @diff @stats
path: root / git@syndamia.com:archive
diff options
context:
space:
mode:
Commit4cdb05b97f24f66f026abc7846b3aff1fc53f71b (patch)
Author
 Syndamia <kamen@syndamia.com>
2024-02-26 10:06:47 +0200
Committer
 Syndamia <kamen@syndamia.com>
2024-02-26 10:06:47 +0200
Files3439a72ea1b9b1221421d01bb11037d7fb8da7fa /git@syndamia.com:archive
csg-4cdb05b97f24f66f026abc7846b3aff1fc53f71b.tar
csg-4cdb05b97f24f66f026abc7846b3aff1fc53f71b.tar.gz
csg-4cdb05b97f24f66f026abc7846b3aff1fc53f71b.zip
Parent6c60778bd3bc3d4b9fda32c9c6d9c412463df31a (diff)
[s1] Combined CSG scripts are now ordered, according to regexes in alphabetically-ordered scripts
Scripts are alphabetically ordered, and combined files use the order in which new regexes (amongst the ordered scripts) are found. By regex I'm reffering to the filename regex as the top comment of every script. This allows some crude amount of control over the order in which scripts are concatenated. Since POSIX doesn't have @include or a similar construct, and the idea is to promote splitting your projects into smaller scripts, this is required. To summarize, all files with the same regex have their rules concatenated in filename alphabetic order, and the rules themselves are ordered, according to their first occurrence in the files in filename alphabetic order. So, rules of script B.awk will always run after script A.awk, no matter regexes. To make script C.awk run before script B.awk, you'll need A.awk and C.awk to share regex, but B.awk to not (A.awk could even be a dummy script, only having the regex on top).
0 files changed, 0 insertions, 0 deletions