bash-bastion / bash-core Goto Github PK

With v1.0.0 coming around the corner, there are a few tasks required

• Remove deprecated functions

  • core.init()
  • core.stacktrace_print()
  • etc.

• Deprecate error handling functions

• Remove error handling functions

• Determine if functions like should_output_color and get_package_info should live here. It seems the should be somewhere else (like bash-utils)

  • Yes, such functions have been deprecated here and moved to bash-std

Override trap and other builtins so no need to remember core functions (on flag or environment variable)

Title

Use bash-error

You could add something like an Errstacktrace

On of my projects.
(https://github.com/yoctu/yosh/blob/master/lib/cli.sh#L60)

It would look like this
/home/dzove855/yosh2/lib/marco.sh: line 4: tik: command not found Error in /home/dzove855/yosh2/lib/marco.sh:4. 'tik' exited with status 127 Call tree: 1: /home/dzove855/yosh2/lib/cli.sh:8 Marco::run(...) 2: yosh2/bin/yosh-runner.sh:78 Cli::router(...) Exiting with status 1

And then you just need to trap ERR so the stackstrace qwill always be call'd when an error happens.

This entails creating a first function for codes that require it (or all of them for consistency) and adding a global variable with $?, since $? will get clobbered

Error if trying to remove a function that no longer exists (or at least warning)

Errors that aren't operational shouldn't have the function name shown in the error output. New functions should be made for those - or as options to existing ones

• Remove function names from core.print_* (Code in ~/.dots depends on this)

• Operational errors should be printed with core.panic(). (if dying is not intended maybe there should be a --no-exit flag

• A die function should also be defined

Title. stderr for error, warn and stdout for info