)]}'
{"functions":[{"author":{"_account_id":5660,"name":"Kurt Taylor","email":"kurt.r.taylor@gmail.com","username":"krtaylor"},"change_message_id":"0a4a5773d384b8cc54f69e6d45c46083847648fc","unresolved":false,"context_lines":[{"line_number":554,"context_line":"function is_arch {"},{"line_number":555,"context_line":"    ARCH_TYPE\u003d$1"},{"line_number":556,"context_line":""},{"line_number":557,"context_line":"    [ \"$(uname -m)\" \u003d\u003d \"$ARCH_TYPE\" ]"},{"line_number":558,"context_line":"}"},{"line_number":559,"context_line":""},{"line_number":560,"context_line":"# Checks if installed Apache is \u003c\u003d given version"}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAATn%2F96nw%3D","line":557,"updated":"2013-12-04 14:42:15.000000000","message":"Question about the string comparison with \"\u003d\u003d\", shouldn\u0027t that be in double brackets \"[[ ]]\"?","commit_id":"fd4a4a4af6e085741b999a4699217b04ce66524c"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"8221bf24ad6e48ea92ea4d7e781b9c30badb85a2","unresolved":false,"context_lines":[{"line_number":554,"context_line":"function is_arch {"},{"line_number":555,"context_line":"    ARCH_TYPE\u003d$1"},{"line_number":556,"context_line":""},{"line_number":557,"context_line":"    [ \"$(uname -m)\" \u003d\u003d \"$ARCH_TYPE\" ]"},{"line_number":558,"context_line":"}"},{"line_number":559,"context_line":""},{"line_number":560,"context_line":"# Checks if installed Apache is \u003c\u003d given version"}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAATn%2F95yE%3D","line":557,"in_reply_to":"AAAATn%2F96hM%3D","updated":"2013-12-04 17:29:02.000000000","message":"While using \u003d\u003d with [ works, it is technically not correct and not portable.  Even though we specify using bash, I\u0027d prefer to not use incorrect idioms as it is a bad habit.  FWIW, using [[ is preferred when the semantic differences with [ are nil.","commit_id":"fd4a4a4af6e085741b999a4699217b04ce66524c"},{"author":{"_account_id":8175,"name":"Rafael Folco","email":"rfolco@redhat.com","username":"rfolco"},"change_message_id":"46ffc24ab98a8f2d1c37cb06731e219fd8f76ee7","unresolved":false,"context_lines":[{"line_number":554,"context_line":"function is_arch {"},{"line_number":555,"context_line":"    ARCH_TYPE\u003d$1"},{"line_number":556,"context_line":""},{"line_number":557,"context_line":"    [ \"$(uname -m)\" \u003d\u003d \"$ARCH_TYPE\" ]"},{"line_number":558,"context_line":"}"},{"line_number":559,"context_line":""},{"line_number":560,"context_line":"# Checks if installed Apache is \u003c\u003d given version"}],"source_content_type":"application/octet-stream","patch_set":2,"id":"AAAATn%2F96hM%3D","line":557,"in_reply_to":"AAAATn%2F96nw%3D","updated":"2013-12-04 16:05:21.000000000","message":"In bash, the \"[\" is bultin so a single bracket is enough for a simple comparison. The double bracket is useful when using \u0026\u0026 or ||.","commit_id":"fd4a4a4af6e085741b999a4699217b04ce66524c"}]}