SQLite format 3 @ � � � .~Z I J� ���b�I ��itablebranchbranch CREATE TABLE `branch` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `repo_id` INTEGER NULL, `name` TEXT NOT NULL, `commit_id` TEXT NULL, `commit_message` TEXT NULL, `pusher_id` INTEGER NULL, `is_deleted` INTEGER NULL, `deleted_by_id` INTEGER NULL, `deleted_unix` INTEGER NULL, `commit_time` INTEGER NULL, `created_unix` INTEGER NULL, `updated_unix` INTEGER NULL)��{tableuseruserCREATE TABLE "user" (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `lower_name` TEXT NOT NULL, `name` TEXT NOT NULL)�!!�OtableattachmentattachmentCREATE TABLE `attachment` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `uuid` UUID NULL, `issue_id` INTEGER NULL, `release_id` INTEGER NULL, `uploader_id` INTEGER DEFAULT 0 NULL, `comment_id` INTEGER NULL, `name` TEXT NULL, `download_count` INTEGER DEFAULT 0 NULL, `size` INTEGER DEFAULT 0 NULL, `created_unix` INTEGER NULL, `repo_id` INTEGER NULL)��utablecommentcommentCREATE TABLE `comment` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `type` INTEGER NULL, `poster_id` INTEGER NULL, `original_author_id` INTEGER NULL, `issue_id` INTEGER NULL, `commit_id` INTEGER NULL, `line` INTEGER NULL, `content` TEXT NULL, `created_unix` INTEGER NULL, `updated_unix` INTEGER NULL, `commit_sha` TEXT NULL, `invalidated` INTEGER NULL, `ref_repo_id` INTEGER NULL, `ref_issue_id` INTEGER NULL, `ref_comment_id` INTEGER NULL, `ref_action` INTEGER NULL, `ref_is_pull` INTEGER NULL)�%%�qtablepull_requestpull_requestCREATE TABLE `pull_request` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `type` INTEGER NULL, `status` INTEGER NULL, `conflicted_files` TEXT NULL, `issue_id` INTEGER NULL, `index` INTEGER NULL, `head_repo_id` INTEGER NULL, `base_repo_id` INTEGER NULL, `head_branch` TEXT NULL, `base_branch` TEXT NULL, `merge_base` TEXT NULL, `has_merged` INTEGER NULL, `merged_commit_id` TEXT NULL, `merger_id` INTEGER NULL, `merged_unix` INTEGER NULL, `commits_ahead` INTEGER NULL, `commits_behind` INTEGER NULL, `changed_protected_files` TEXT NULL, `flow` INTEGER DEFAULT 0 NOT NULL, `allow_maintainer_edit` INTEGER DEFAULT 0 NOT NULL)�b�#tableissueissueCREATE TABLE `issue` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `repo_id` INTEGER NULL, `index` INTEGER NULL, `poster_id` INTEGER NULL, `original_author` TEXT NULL, `original_author_id` INTEGER NULL, `name` TEXT NULL, `content` TEXT NULL, `milestone_id` INTEGER NULL, `priority` INTEGER NULL, `is_closed` INTEGER NULL, `is_pull` INTEGER NULL, `num_comments` INTEGER NULL, `ref` TEXT NULL, `deadline_unix` INTEGER NULL, `created_unix` INTEGER NULL, `updated_unix` INTEGER NULL, `closed_unix` INTEGER NULL, `is_locked` INTEGER DEFAULT 0 NOT NULL, `pin_order` INTEGER DEFAULT 0 NULL)P++Ytablesqlite_sequencesqlite_sequenceCREATE TABLE sqlite_sequence(name,seq)�3!!�1tablerepositoryrepositoryCREATE TABLE `repository` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `owner_id` INTEGER NULL, `lower_name` TEXT NOT NULL, `name` TEXT NOT NULL, `description` TEXT NULL, `default_branch` TEXT NULL, `num_watches` INTEGER NULL, `num_stars` INTEGER NULL, `num_forks` INTEGER NULL, `num_issues` INTEGER NULL, `num_closed_issues` INTEGER NULL, `num_pulls` INTEGER NULL, `num_closed_pulls` INTEGER NULL, `status` INTEGER DEFAULT 0 NOT NULL, `is_fork` INTEGER DEFAULT 0 NOT NULL, `fork_id` INTEGER NULL, `size` INTEGER DEFAULT 0 NOT NULL, `created_unix` INTEGER NULL, `updated_unix` INTEGER NULL, `owner_name` TEXT NULL, `git_size` INTEGER DEFAULT 0 NOT NULL) ) W�m � 4�) b7 =bc_libsbc_libsLibraries for bc and dc.master ���`He�M�gavin ��Ɓ$) �W bcbcAn implementation of Unix dc and POSIX bc with GNU and BSD extensions. Finished, but well-maintained.master �Y�_�0�_�4�mcf �Y��,( �W#bcbcAn implementation of Unix dc and POSIX bc with GNU and BSD extensions. Finished, but well-maintained.master ���_s�I_t��brooksdavis ��́" �bcbcAn implementation of Unix dc and POSIX bc with GNU and BSD extensionsmaster ��_)�d_)�xry111 ��� �bcbcAn implementation of Unix dc and POSIX bc with GNU and BSD extensionsmaster �=�^�\�^�h�e5ten �=�_ ?vim-bcvim-bcvim syntax file for my bcmaster )%^���d���gavin)%�& �WbcbcAn implementation of Unix dc and POSIX bc with GNU and BSD extensions. Finished, but well-maintained.master ��7^�d>g�`�gavin��7 � ������� branch userCcommentl%pull_request issueG!attachment�!repository: � � � ������� � ;� /�Seg fault in make checkI use your AUR PKGBUILD. Obviously the executable doesn't have debugging symbols, but I can figure out how to compile with them if you need. ``` Running bc errors..../tests/errors.sh: line 101: 107555 Done printf '%s\n' "$line" 107556 Segmentation fault (core dumped) | "$exe" "$@" "$options" 2> "$out" > /dev/null bc crashed (139) on test: j(1,2,3) make: *** [Makefile:349: test_bc_error_lines] Error 139 ```refs/heads/mastera�IMaÙ�aÙ�+ Y�O Please stop updating copyright noticesThere is no legal reason to update a copyright notice: your copyright will subsist until you are seventy years dead and then cease. People who understand what _finished_ means shouldn't need to look at a copyright date either. So what you are doing is making changes for the sake of making changes, which is just as bad in the comments as in the code.`@�`@A�`@A�� Y� syntax error near unexpected token `)'For bc-3.2.5, runing 'sh configure.sh' I get👍 configure.sh: line 612: syntax error near unexpected token `)' configure.sh: line 612: ` disable-extra-math*)'`��`�`�� m� Avoid clobbering `r` variable in Bessel function The `j` function uses `r` to accumulate its result, but did not declare it with auto, causing the caller's value to be clobbered. To fix this, declare `r` as auto to make it a local variable._�5*_��#_��U�B E� Passify a new clang warning. Clang 12 warns about certain cases of string concatenation in array initialization. Adding parentheses siliences this warning._s��_t�(_t��R a� fix buggy format string in zh_CN.UTF-8.msgSeveral strings in `zh_CN.UTF-8.msg` are buggy. The most alerming one is the translation of ~~~~~ 6 "invalid command-line option: \"%s\"" ~~~~~ The translation in `zh_CN.UTF-8.msg` is: ~~~~~ 6 "无效的命令行选项:'%c'(\"%s\")" ~~~~~ We can see the format string is not matched. This causes `make test` fail (`dc` crashes). I think we should add a `locale_check.sh`, to check if all format strings in translations match to the original English string. But I'm too lazy to do that, at least for now :)._)�5_*) _*#݆ o� `locale_install.sh` fails to install many localesHi Gavin, In `locale_install.sh`, it lists all installed locales with `locale -a`, then tries to match all `.msg` files in `locales` with them. If one `.msg` files matches a installed locale, it will be installed. Unfortunately, on my LFS development system (with glibc-2.31) `locale -a` outputs the locale names like `zh_CN.utf8`, but the corresponding `.msg` file is `zh_CN.UTF-8.msg`. Then it just won't be installed. I can create a symlink `zh_CN.utf8.msg` to `zh_CN.UTF-8.msg` to make `locale_install.sh` install it. But I'm not sure if it's the best way to solve this problem. (This is just an example, there are many other mismatches like `en_US.ISO8859-1.msg` versus `en_US.iso88591`, etc.)^�T^�wD^�wD�' � � replace strdup use with malloc+memcpy, to remove _XOPEN_SOURCEsupercedes #1, keeps POSIX version at 2001, removes XSI requirement.^�h^� 4^� 4�V w� bump _POSIX_C_SOURCE to 200809L, remove _XOPEN_SOURCEWith the previous `_POSIX_C_SOURCE=200112L`, strdup was the only function that was unavailable without `_XOPEN_SOURCE=600`, increase `_POSIX_C_SOURCE` version to make it so `_XOPEN_SOURCE` can be removed and the source can be completely POSIX compatible.^�^c^�7�^� � � �5� � x ] ] [])besselmastera3a2eba6662db5c57a4d77cc8cb3ec1d8269c646021527d2bcbf531534fc344e8be4b250bb16c6d0_��V� O] ] [](bugprone-suspicious-missing-commamasterfa9bcc02531b1b54024d25feb7c7dd083e6b02c207f80644ddb4ec93f4bd1e1455aad65cb57bcb6c_t��~ )] ] []"xry111-patch-1masterccad710baf848775bfa6d72bf62bf6c5f0a4eab99cb586fc2981bc6813b685d6b136cbdb00504109_*#�R ] []no-xsimaster6f5fdd4ff62723ed95818f3d830d810267d9fe15_W��u ] ] []posix-cmaster6f5fdd4ff62723ed95818f3d830d810267d9fe15a054de4b1e6dc61e493de72176faf0aa7236a5d3^� � � ����ug�7 � � t L & ^� 4^� 4 Q c I've reopened my previous PR that did that.^� 2^� 2 & ^� !^� ! F M Fair enough. Let's do that then.^�^� � �= imo if you don't want to replace the strdup, I think POSIX 2008 would be a better requirement than POSIX and XSI 2001, because a POSIX compliant would have to be 12 years out of date to not support POSIX 2008, but a hypothetical OS seeking purely to comply to POSIX could potentially never end up complying to XSI 2001 or supporting the define.^�^� Q c I would, yes. Hmm...back to thinking again.^��^�� Y s But you would still need the XSI define for strdup?^��^�� �/ � After considering this, I think it would be better to just change the requirements from POSIX 2001 and XSI to POSIX 2001 and `strdup()`.^���^��� �Y �q Fair enough. In regards to speed I just checked glibc, musl, and freebsd's libc's implementations of strdup, and they all do strlen+malloc+memcpy, so I would expect that's the case in most places and there shouldn't be a significant speed difference. EDIT: same for openbsd's libc, uclibc{,-ng}, and bionic^��F^��� �F �K I have done some research and confirmed what you said about `c99` being part of the `CD` group. That said, this is a hard decision. I found some [benchmarks that show that `strdup()` can be faster than `strlen()`/`malloc()`/`memcpy()`][1]. Note that it is not in most cases, but it *is* always the same or better. I am also not sure that this requirement is a burden in practice since `strdup()` is also technically required by POSIX 2008 base and XSI also requires `c99` and `make`. I mean, I could move back to requiring POSIX 2008, but I also admit that I would be surprised if there was a platform that did not support XSI 2001. I don't know. I will have to think about this one. I will keep it open in the meantime. [1]: https://www.vanheusden.com/misc/strdup/strdup_v_SlMalMemc.php^�|^�| �" � It hasn't caused me any build trouble at all, I'm on a very normal platform. I just thought it could be preferable to make the build completely POSIX compliant, if possible. In regards to `c99`, it isn't an XSI extension, it's part of the `CD` (C development utilities) option group, which is pretty much needed for C programs, like `bc`. A similar option group that is also technically optional functionality is the `SD` (software development utilities) group, which `make` that `bc` also requires is a part of. As far as I can tell the only thing requiring the XSI option group in this project is that one strdup use the PR replaces.^��L^��L � �Y Thank you for your PR. Can you tell me a little more about why you would like to remove the XSI requirement? Is it making it difficult for you to build on your platform? Also, be aware that technically, `c99`, a requirement for `bc`, is part of XSI, so I am not sure the requirement could be removed. However, I would love to hear why you want it removed.^�|b^�|b �5 �) This actually allows the source to compile with `_POSIX_C_SOURCE=1` if you want. EDIT: nevermind, I had certain functionality disabled that uses stuff present with `_POSIX_C_SOURCE=200112L` but not `_POSIX_C_SOURCE=1`. EDIT 2: specifically, the only thing that needs `_POSIX_C_SOURCE=200112L` and isn't available with `_POSIX_C_SOURCE=1` is pselect, and subsequently the timespec struct used by it.^�lL^�� & ^�h�^�h� & ^�h^�h � �C Alternatively, if you would prefer the POSIX requirement stay at 2001, I could just replace the one actual strdup call with a malloc+memcpy, and then `_POSIX_C_SOURCE=200112L` without `_XOPEN_SOURCE` will be sufficient C , � ������� �z0��P � r ( � � J �l"��D��f��>��`�|2��N�m � � K5 U 3 22df2984-da83-4738-a520-da20e7f70a601bc-2.5.2.tar.xz.sig\�^��pH4 U + 6e32993d-66fd-42a1-9f5f-bb1ca3e8d0d00bc-2.5.1.tar.xzSzh^��8K3 U 3 220be9a3-d6d6-4cd1-861f-0d9106bd09a20bc-2.5.1.tar.xz.sigY�^��8H2 U + a3007381-ba5d-4892-8649-60d40541ea3a/bc-2.5.0.tar.xzZw�^���K1 U 3 174b1a57-79f5-4b27-a26d-6496f7a2cfef/bc-2.5.0.tar.xz.sigW�^���H0 U + 77234f0f-7932-4a96-bf5f-2e68ea3d0619.bc-2.4.0.tar.xzO�@^��~K/ U 3 ee97f429-e251-445e-a6cf-8da572746d11.bc-2.4.0.tar.xz.sigK�^��~H. U + 9d77563f-0956-49c7-945a-976dc630b5ec-bc-2.3.2.tar.xzLqx^��K- U 3 c4e92e0d-25ed-4dfe-89ac-ced8e94c3252-bc-2.3.2.tar.xz.sigO�^��H, U + 5efad9e6-d7fa-4994-9b5a-f29dfdc6edb9,bc-2.3.1.tar.xzgw�^���K+ U 3 35022279-0992-4177-8335-65a970786169,bc-2.3.1.tar.xz.sigt�^���K* U 3 a263849b-6399-4a81-85dc-ac528a8480bf+bc-2.3.0.tar.xz.sigR�^��H) U + d6dc1fa9-b28f-4ffe-b350-854d08c2f2f6+bc-2.3.0.tar.xzMv�^��H( U + 4fc4e50d-eede-47fe-bb2a-2ade1c690bb2*bc-2.2.0.tar.xzLZ�^���H' U + aea71e5f-f202-4690-86bf-4bc0fc1a8fdc*bc-2.2.0.tar.xzOZ�^��nH& U + 7fb79089-29b0-4f7b-afec-6fdb6645e8b0)bc-2.1.3.tar.xzJU�^��8H% U + 31676840-3d19-4afa-8d03-899cb31bba56(bc-2.1.2.tar.xzH�<^��dH$ U + 0eea5c02-ac06-4928-9d21-b511c6f39254'bc-2.1.1.tar.xzEV�^��*H# U + 1a039682-929e-46da-8a07-d2c93e99fe41&bc-2.1.0.tar.xzJY8^���H" U + de121f6f-dd68-4e2f-b629-fe6099cf4757%bc-2.0.3.tar.xzFz8^��vH! U + 0f87e84f-6244-4db2-9e59-c775a102293f$bc-2.0.2.tar.xzFA�^��1H U + b137f55a-5e79-4d82-96a6-394cb201e461#bc-2.0.1.tar.xzY@�^���H U + a8794742-ef79-41ca-b731-ce94867dc3b2"bc-2.0.0.tar.xzK>�^���H U + 70b4b90f-b4a2-497b-8c3f-0a8001ab92d4!bc-1.2.8.tar.xzH��^���H U + 32d51ac8-674f-4e9a-b05f-b72197abff3a bc-1.2.7.tar.xzE�^���H U + 52eb84a1-a347-4d37-923c-14a227eacd66bc-1.2.6.tar.xzN�H^��H U + 35591e8f-d2f8-4f9d-ad54-f640b658462ebc-1.2.5.tar.xzT��^���H U + b6b5876f-3955-4605-9461-916bbcadc49cbc-1.2.4.tar.xzT�<^��nH U + 85f29daf-22f2-48cc-a772-b3c21925be7abc-1.2.3.tar.xzE��^���H U + 085d7969-42a1-4d8b-9cf3-7abaed11027fbc-1.2.2.tar.xzI�0^��IH U + fb46796b-d2c4-4dfa-8c4f-de74d20f8a96bc-1.2.1.tar.xzRմ^���H U + 0dc34cfa-bc92-4f54-a588-2b298470a13ebc-1.2.0.tar.xzMՠ^��]H U + 949b6363-8225-4b74-962f-21b785cf199ebc-1.1.4.tar.xzN�X^���H U + 11693cc3-acb1-4598-930a-03649664ec7ebc-1.1.3.tar.xzU��^���H U + 4fd9711f-77d3-41af-8199-0103f4e8a3fabc-1.1.2.tar.xzM��^��`H U + e4e43dff-8383-4040-8d7b-2653dfde0f34bc-1.1.1.tar.xzV��^���H U + 0592b786-1c97-4d09-9816-634733a645eebc-1.1.0.tar.xzS��^���I U - e0d708b0-c143-4546-abe8-438b76d7a2cfbc-1.1rc3.tar.xzRm�^���I U - 4a4d099f-ae2d-4785-af8d-847a7fac4b7abc-1.1rc2.tar.xzTmp^��dH U + a3890a2d-99b5-4ac0-9084-58db95443316bc-1.1b5.tar.xzWn�^��(H U + f10b0375-605f-404b-abd4-7fad0c4cd206bc-1.1b4.tar.xzPn�^��hH U + c2740a7d-6a54-4873-9703-75a3c4d660bebc-1.1b3.tar.xzIn�^�� H U + 8bd7740f-1c09-451f-90e4-981fc35a7f6abc-1.1b2.tar.xzPm�^���H U + ee274fe2-26d5-4b07-8269-cd18576c3437 bc-1.1b1.tar.xzOo@^���J U / 4f727ba6-57e7-40d2-9d6d-9653ff8d916abc-1.1-rc1.tar.xzTp|^��5F U ' 2268656b-5e1a-4f4f-b2e1-5a2da65919cbbc-1.0.tar.xzH�^��sJ U / 8fb0a31d-7c63-44ae-8bda-6f3d99ec35d3 bc-1.0-rc7.tar.xzE ��^���J U / f2373938-46a5-47f4-a787-abb0859cacb2 bc-1.0-rc6.tar.xzG ��^��3J U / 662acdfd-5d11-437f-9b69-7c43d7abf572bc-1.0-rc5.tar.xzI �$^���J U / 80f744d9-923c-4716-8e9b-985cee4f247fbc-1.0-rc4.tar.xzD ��^��J U / fe378537-73c3-4264-8f09-0ff1d8e0605cbc-1.0-rc3.tar.xzM ��^���J U / 792cd230-8147-4c5e-8fb8-74ab1e7fff81bc-1.0-rc2.tar.xzJ �X^��OJ U / d5cc3936-c05e-480f-955 � �R � �m �. u 5 f �������f !!johnwcowanjohnwcowan bdubbsbdubbs mcfmcf ##brooksdavisbrooksdavis xry111xry111 e5tene5ten stesserstesser gavingavin � �F�k � (�C�O � [ � u����� x ]q(rand0401b53c37c482a1df892174536ddaa3b29120fcUpdate the Binary Size section of the build manual^���e@�e@�i ]M(signalsad8b325ce3377e4ca030623269fc45b4fbb8c0f7Start adding my own buffered I/O^Ĭ$e@�e@�h ]M(master9487714deb6d80818a8f7f4cd32fe8bd8e86a83fFix the Chinese locales for real_*Hpe@�e@�� O]�(bugprone-suspicious-missing-commaaebde4eb1b66737d686f56fd56cc35814dd43e36Merge branch 'master' into bugprone-suspicious-missing-comma_t��e@�e@�k ]Qsignals0eaeaa9175daaab345e62ed4edfc8485aa9beb77Merge branch 'master' into signals^�Ĭex��ex��x ]qrand0401b53c37c482a1df892174536ddaa3b29120fcUpdate the Binary Size section of the build manual^���ex��ex��d ]Emaster6f5fdd4ff62723ed95818f3d830d810267d9fe15Make a test run more quickly^�1!ex��ex��~ ]wposix-c583099c99e32a00de43145272cc7258c4359a272bump _POSIX_C_SOURCE to 200809L, remove _XOPEN_SOURCE^�d8ex��ex��� ]� no-xsie6466e4576cee396d95819c8dcd6439376bb20b1replace strdup use with malloc+memcpy, to remove _XOPEN_SOURCE^�hiex��ex��h ]K)library70922bc23a702549c362a2687c7a110f1e5b575eRemove the neg field from BcNum_�hAex��ex��x ]m)master0079ec0553df264fdb1a978734936742ff3c3cb0Avoid clobbering `r` variable in Bessel function_�2�ex��ex��x ]m)bessel0079ec0553df264fdb1a978734936742ff3c3cb0Avoid clobbering `r` variable in Bessel function_�2�ex��ex��x ]q)rand0401b53c37c482a1df892174536ddaa3b29120fcUpdate the Binary Size section of the build manual^���ex��ex��i ]M)signalsad8b325ce3377e4ca030623269fc45b4fbb8c0f7Start adding my own buffered I/O^Ĭ$ex��ex��x ]q"rand0401b53c37c482a1df892174536ddaa3b29120fcUpdate the Binary Size section of the build manual^���ex�Oex�Oi ]M"signalsad8b325ce3377e4ca030623269fc45b4fbb8c0f7Start adding my own buffered I/O^Ĭ$ex�Oex�O\ ]5"masterccad710baf848775bfa6d72bf62bf6c5f0a4eab9Tweak the NEWS again_( �ex�Oex�Oz )]a"xry111-patch-1edc0673e04a7a546dff8d0253130998a77f4f0f4fix buggy format string in zh_CN.UTF-8.msg_)�ex�Oex�O] ]7 7master0825561931128d69588ac2c2ed8c1cf78a513960Fix precedence issuese�M�ej�e�M�Z ]1master3c420d7fe4ab3b16cad9da69e688bdecaa724f2dAdd a basic READMEd��qeg�eg�\ ]7 master437ea4efc12bd28644118a7fa18b255ffe61bbadAdd more to a warningg�`^eepg�`� L ����c�ug�7 � � t L & ^� 4^� 4 Q c I've reopened my previous PR that did that.^� 2^� 2 & ^� !^� ! F M Fair enough. Let's do that then.^�^� � �= imo if you don't want to replace the strdup, I think POSIX 2008 would be a better requirement than POSIX and XSI 2001, because a POSIX compliant would have to be 12 years out of date to not support POSIX 2008, but a hypothetical OS seeking purely to comply to POSIX could potentially never end up complying to XSI 2001 or supporting the define.^�^� Q c I would, yes. Hmm...back to thinking again.^��^�� Y s But you would still need the XSI define for strdup?^��^�� �/ � After considering this, I think it would be better to just change the requirements from POSIX 2001 and XSI to POSIX 2001 and `strdup()`.^���^��� �Y �q Fair enough. In regards to speed I just checked glibc, musl, and freebsd's libc's implementations of strdup, and they all do strlen+malloc+memcpy, so I would expect that's the case in most places and there shouldn't be a significant speed difference. EDIT: same for openbsd's libc, uclibc{,-ng}, and bionic^��F^��� �F �K I have done some research and confirmed what you said about `c99` being part of the `CD` group. That said, this is a hard decision. I found some [benchmarks that show that `strdup()` can be faster than `strlen()`/`malloc()`/`memcpy()`][1]. Note that it is not in most cases, but it *is* always the same or better. I am also not sure that this requirement is a burden in practice since `strdup()` is also technically required by POSIX 2008 base and XSI also requires `c99` and `make`. I mean, I could move back to requiring POSIX 2008, but I also admit that I would be surprised if there was a platform that did not support XSI 2001. I don't know. I will have to think about this one. I will keep it open in the meantime. [1]: https://www.vanheusden.com/misc/strdup/strdup_v_SlMalMemc.php^�|^�| �" � It hasn't caused me any build trouble at all, I'm on a very normal platform. I just thought it could be preferable to make the build completely POSIX compliant, if possible. In regards to `c99`, it isn't an XSI extension, it's part of the `CD` (C development utilities) option group, which is pretty much needed for C programs, like `bc`. A similar option group that is also technically optional functionality is the `SD` (software development utilities) group, which `make` that `bc` also requires is a part of. As far as I can tell the only thing requiring the XSI option group in this project is that one strdup use the PR replaces.^��L^��L � �Y Thank you for your PR. Can you tell me a little more about why you would like to remove the XSI requirement? Is it making it difficult for you to build on your platform? Also, be aware that technically, `c99`, a requirement for `bc`, is part of XSI, so I am not sure the requirement could be removed. However, I would love to hear why you want it removed.^�|b^�|b �5 �) This actually allows the source to compile with `_POSIX_C_SOURCE=1` if you want. EDIT: nevermind, I had certain functionality disabled that uses stuff present with `_POSIX_C_SOURCE=200112L` but not `_POSIX_C_SOURCE=1`. EDIT 2: specifically, the only thing that needs `_POSIX_C_SOURCE=200112L` and isn't available with `_POSIX_C_SOURCE=1` is pselect, and subsequently the timespec struct used by it.^�lL^�� & ^�h�^�h� & ^�h^�h � �C Alternatively, if you would prefer the POSIX requirement stay at 2001, I could just replace the one actual strdup call with a malloc+memcpy, and then `_POSIX_C_SOURCE=200112L` without `_XOPEN_SOURCE` will be sufficient.^�e�^�e� ? ��S 6� � e�^���P �4��? v ? 5, + Release is out!_��#_��# �F+ �K Sorry, I didn't mean that what you did wasn't valuable. I obviously didn't catch it. What I meant is that is was obvious that your fix was good. Words..._���_��� � * �Q Obvious bug is obvious, and obvious fix is obvious. I will put out a release very soon. Thank you!_��r_��r &) _��U_��U �>( �k] <a href="/gavin/bc/commit/021527d2bcbf531534fc344e8be4b250bb16c6d0">Merge pull request 'Avoid clobbering `r` variable in Bessel function' (#7) from mcf/bc:bessel into master Reviewed-on: https://git.yzena.com/gavin/bc/pulls/7 </a>_��U_��U021527d2bcbf531534fc344e8be4b250bb16c6d0 �!' � Thank you very much. And thanks for reporting it to FreeBSD also; the package maintainer over there and I were in contact._t�(_t�( && _t��_t�� �M% � ] <a href="/gavin/bc/commit/07f80644ddb4ec93f4bd1e1455aad65cb57bcb6c">Merge pull request 'Passify a new clang warning.' (#6) from brooksdavis/bc:bugprone-suspicious-missing-comma into master Reviewed-on: https://git.yzena.com/gavin/bc/pulls/6 </a>_t��_t��07f80644ddb4ec93f4bd1e1455aad65cb57bcb6c �$ �c I encountered this compiling FreeBSD-CURRENT with the latest llvm-devel port (a snapshot dated 2020-09-25)._s�_s� �# �m Thank you for the fix. It has been merged, and I will be pushing fixes for the rest of the Chinese locales soon._*) _*) &" _*#�_*#� �! �] <a href="/gavin/bc/commit/9cb586fc2981bc6813b685d6b136cbdb00504109">Merge pull request 'fix buggy format string in zh_CN.UTF-8.msg' (#5) from xry111/bc:xry111-patch-1 into master </a>_*#�_*#�9cb586fc2981bc6813b685d6b136cbdb00504109 �# � Thank you for the report and the code. I will commit this when I get home. I will also check all of the messages in Chinese._)��_)�� & ^�wD^�wD �\ �w Okay, I have added all of the `utf8` locales. It was big enough of a change that I decided to release `3.0.2`. I am closing this now; please reopen if there is more I need to do.^�wB^�wB �v �+ It's not critical so I can wait for the next release. I only use zh_CN.utf8 locale (besides the well-known locales `C` or `en_US.utf8`). But as recent glibc version's `locale -a` only outputs `utf8` instead of `UTF-8` now, each `UTF-8` should be added an `utf8` symlink (IMO). For example, `es_ES.utf8.msg`, `ja_JP.utf8.msg`, etc.^�I^�I �y �1 Symlinks are best, yes. I don't add them until someone asks because I don't know what is needed. I have added a symlink to zh_CN.utf8. Do you need me to do a release? Also, are there other symlinks you want?^�N�^�N� �Y �q So...it turns out that `LONG_BIT` is also under X/Open System Interfaces. And I need this one because it defaults to the minimum of 32 if it doesn't exist. Because of that, I have to undo this PR merge and go back to using XSI. And since I am doing that, might as well go back to POSIX 2001 and XSI 600.^�7�^�7� �P �_ Oh, I should note that even though I have made improvements to `bc` apart from this PR, I won't be releasing a new version for a while. Expect about two or three months.^�!d^�!d H Q No problem, it was a tough choice!^�!^�! K W Thanks. I apologize for the waffling.^� �^� � & ^� �^� � �5 �Y] <a href="/gavin/bc/commit/a054de4b1e6dc61e493de72176faf0aa7236a5d3">Merge pull request #1 Pull request description: > bump _POSIX_C_SOURCE to 200809L, remove _XOPEN_SOURCE' (#1) > from e5ten/bc:posix-c into master </a>^� �^� �a054de4b1e6dc61e493de72176faf0aa7236a5d3 � \ � �z�c�<� �`C �} � Oh I didn't realize I wouldn't get email notifications. Yeah, that worked @kseistrup. That seems a reasonable change in the PKGBUILD. So your changes don't work with unicode, @gavin? Also I didn't realize someone else had taken up the AUR package maintainer role. I would have submitted this there first. a��a�� �B �w � @brodygoat, I have edited the `PKGBUILD` to set `LANG=C` and `LC_ALL=C`. Could you see if this solves your problem? a��'a��'