Return to Question

Without ;;&, /bin/sh gives Syntax error: ")" unexpected (expecting ";;").

;;& triggers shellcheck's ^-- SC2127 (error): To use cases with ;;&, specify #!/usr/bin/env bash notice.

Other than not use /bin/sh, how to fallthrough? Have no wish to use /bin/sh, but /bin/sh is the "lowest common denominator" (which all Unix consoles are supersets), so cross-platform code is supposed to use this.

The specific use for this particular fallthrough is this function, which has this switch:

        case "${5}" in #/* Language determines which flags to use */
            "C")
                export CFLAGS="${CFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}"
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" #/* As far as lib support, C++ is a superset */
                ;;
            "C++")
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";;
            *) #/* Include flags for unknown languages export to all build scripts */
                export FLAGS_USER="${FLAGS_USER} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";; #/* Todo: allow to use this after `SUSUWU_SETUP_BUILD_FLAGS()` */
        esac

The wish is to remove the duplicate export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" if the "C" codeflow can fallthrough to the "C++" codeflow.

• The reason to remove duplicate code is to reduce the risk that future versions (with more code) will end up with 1 flow updated out-of-sync with the other flow.

Without ;;&, /bin/sh gives Syntax error: ")" unexpected (expecting ";;").

;;& triggers shellcheck's ^-- SC2127 (error): To use cases with ;;&, specify #!/usr/bin/env bash notice.

Other than not using /bin/sh, how to fallthrough? Have no wish to use /bin/sh, but /bin/sh is the "lowest common denominator" (of which all Unix shells are supersets), so cross-platform code is supposed to use this.

The specific use for this particular fall-through is this function, which has this switch:

        case "${5}" in #/* Language determines which flags to use */
            "C")
                export CFLAGS="${CFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}"
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" #/* As far as lib support, C++ is a superset */
                ;;
            "C++")
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";;
            *) #/* Include flags for unknown languages export to all build scripts */
                export FLAGS_USER="${FLAGS_USER} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";; #/* Todo: allow to use this after `SUSUWU_SETUP_BUILD_FLAGS()` */
        esac

The wish is to remove the duplicate export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" if the "C" code flow can fall through to the "C++" code flow.

The reason to remove duplicate code is to reduce the risk that future versions (with more code) will end up with 1 flow updated out-of-sync with the other flow.

Without ;;&, /bin/sh gives Syntax error: ")" unexpected (expecting ";;").

;;& triggers shellcheck's ^-- SC2127 (error): To use cases with ;;&, specify #!/usr/bin/env bash notice.

Other than not use /bin/sh, how to fallthrough? Have no wish to use /bin/sh, but /bin/sh is the "lowest common denominator" (which all Unix consoles are supersets), so cross-platform code is supposed to use this.

The specific use for this particular fallthrough is this function, which has this switch:

        case "${5}" in #/* Language determines which flags to use */
            "C")
                export CFLAGS="${CFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}"
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" #/* As far as lib support, C++ is a superset */
                ;;
            "C++")
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";;
            *) #/* Include flags for unknown languages export to all build scripts */
                export FLAGS_USER="${FLAGS_USER} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";; #/* Todo: allow to use this after `SUSUWU_SETUP_BUILD_FLAGS()` */
        esac

. The wish is to remove the duplicate export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" if the "C" codeflow can fallthrough to the "C++" codeflow.

Without ;;&, /bin/sh gives Syntax error: ")" unexpected (expecting ";;").

;;& triggers shellcheck's ^-- SC2127 (error): To use cases with ;;&, specify #!/usr/bin/env bash notice.

Other than not use /bin/sh, how to fallthrough? Have no wish to use /bin/sh, but /bin/sh is the "lowest common denominator" (which all Unix consoles are supersets), so cross-platform code is supposed to use this.

The specific use for this particular fallthrough is this function, which has this switch:

        case "${5}" in #/* Language determines which flags to use */
            "C")
                export CFLAGS="${CFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}"
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" #/* As far as lib support, C++ is a superset */
                ;;
            "C++")
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";;
            *) #/* Include flags for unknown languages export to all build scripts */
                export FLAGS_USER="${FLAGS_USER} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";; #/* Todo: allow to use this after `SUSUWU_SETUP_BUILD_FLAGS()` */
        esac

The wish is to remove the duplicate export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" if the "C" codeflow can fallthrough to the "C++" codeflow.

• The reason to remove duplicate code is to reduce the risk that future versions (with more code) will end up with 1 flow updated out-of-sync with the other flow.

Without ;;&, /bin/sh gives Syntax error: ")" unexpected (expecting ";;").

;;& triggers shellcheck's ^-- SC2127 (error): To use cases with ;;&, specify #!/usr/bin/env bash notice.

Other than not use /bin/sh, how to fallthrough?

Without ;;&, /bin/sh gives Syntax error: ")" unexpected (expecting ";;").

;;& triggers shellcheck's ^-- SC2127 (error): To use cases with ;;&, specify #!/usr/bin/env bash notice.

Other than not use /bin/sh, how to fallthrough? Have no wish to use /bin/sh, but /bin/sh is the "lowest common denominator" (which all Unix consoles are supersets), so cross-platform code is supposed to use this.

The specific use for this particular fallthrough is this function, which has this switch:

        case "${5}" in #/* Language determines which flags to use */
            "C")
                export CFLAGS="${CFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}"
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" #/* As far as lib support, C++ is a superset */
                ;;
            "C++")
                export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";;
            *) #/* Include flags for unknown languages export to all build scripts */
                export FLAGS_USER="${FLAGS_USER} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}";; #/* Todo: allow to use this after `SUSUWU_SETUP_BUILD_FLAGS()` */
        esac

. The wish is to remove the duplicate export CXXFLAGS="${CXXFLAGS} ${1}${SUSUWU_DEPENDENCY_INCLUDE_PATH}" if the "C" codeflow can fallthrough to the "C++" codeflow.