You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be great if flatten could track what functions are really used. And then if possible, - variables.
Maybe it is done already in the flatten, I not looked at this time.
If flattened scripts deliberately have some sort of additional info for shellfire development after, flatten can have a option --strip
Like start from: core_init_main "$@" and recursively check what functions use what functions.
And; as script has the only one entry point, root node - core_init_main - that means all functions not connected with core_init_main can be cleaned-out.
Basic overdrive example parses example right after flatten. So I see it probably works well without unconnected functions.
The text was updated successfully, but these errors were encountered:
Would be great if
flatten
could track what functions are really used. And then if possible, - variables.Maybe it is done already in the
flatten
, I not looked at this time.If flattened scripts deliberately have some sort of additional info for shellfire development after,
flatten
can have a option--strip
Like start from:
core_init_main "$@"
and recursively check what functions use what functions.And; as script has the only one entry point, root node -
core_init_main
- that means all functions not connected withcore_init_main
can be cleaned-out.Basic
overdrive
example parses example right afterflatten
. So I see it probably works well without unconnected functions.The text was updated successfully, but these errors were encountered: