ruby.git/ext/win32ole/win32ole.c, branch v3_3_11 The Ruby Programming Language [ruby/win32ole] Bump up 1.8.10 2023-11-07T05:52:50+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2023-11-07T05:52:36+00:00 eaf0ca4cfe7d7b53c3812b593a5e49db5dff9c74 https://github.com/ruby/win32ole/commit/9a18f388a9 
https://github.com/ruby/win32ole/commit/9a18f388a9
[ruby/win32ole] Reuse WIN32OLE_VERSION for gem version 2023-04-21T04:46:10+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2023-04-21T04:34:55+00:00 b9b43a10202573431ae211984b02c28792f58ef8 https://github.com/ruby/win32ole/commit/bff3ea8b0b 
https://github.com/ruby/win32ole/commit/bff3ea8b0b
Expand tabs [ci skip] 2022-07-21T16:42:04+00:00 Takashi Kokubun takashikkbn@gmail.com 2022-07-21T16:23:58+00:00 5b21e94bebed90180d8ff63dad03b8b948361089 [Misc #18891] 
[Misc #18891]
[ruby/win32ole] Get rid of potential undefined behavior 2022-03-14T23:33:40+00:00 xtkoba 69125751+xtkoba@users.noreply.github.com 2021-05-09T00:18:52+00:00 63b1633f869d6866ed70dbf80efc954d26127a04 See https://bugs.llvm.org/show_bug.cgi?id=50236 https://github.com/ruby/win32ole/commit/019ec2b3cb 
See https://bugs.llvm.org/show_bug.cgi?id=50236

https://github.com/ruby/win32ole/commit/019ec2b3cb
Fix `_MSC_VER` warnings 2021-06-02T15:07:25+00:00 Daisuke Fujimura (fd0) booleanlabel@gmail.com 2021-05-12T22:22:08+00:00 e451f0f678b88f9634712856c4a5e45b7d3ca7dc 






Add string encoding IBM720 alias CP720 (#3803)
2020-11-22T13:23:40+00:00

Lars Kanis
lars@greiz-reinsdorf.de

2020-11-22T13:23:40+00:00

d403591b34e204a5937241025c62c877e579fbaf

The mapping table is generated from the ICU project:
  https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-720_P100-1997.ucm

Fixes bug 16233 : https://bugs.ruby-lang.org/issues/16233




The mapping table is generated from the ICU project:
  https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-720_P100-1997.ucm

Fixes bug 16233 : https://bugs.ruby-lang.org/issues/16233






win32ole: separate global variable declarations and definitions
2020-05-10T12:37:59+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2020-05-10T12:35:54+00:00

f1699314147bad2cf5550cc582693424fdbc2510

https://gcc.gnu.org/gcc-10/changes.html#c

> * GCC now defaults to `-fno-common`.  As a result, global
>   variable accesses are more efficient on various targets.  In
>   C, global variables with multiple tentative definitions now
>   result in linker errors.  With `-fcommon` such definitions are
>   silently merged during linking.





https://gcc.gnu.org/gcc-10/changes.html#c

> * GCC now defaults to `-fno-common`.  As a result, global
>   variable accesses are more efficient on various targets.  In
>   C, global variables with multiple tentative definitions now
>   result in linker errors.  With `-fcommon` such definitions are
>   silently merged during linking.







Suppress C4267 "possible loss of data" warnings
2020-04-17T00:24:46+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2020-04-16T23:14:38+00:00

75a0447c15a7ab017bd4240c2a9cc69b134b80b9

Just cast down explicitly.





Just cast down explicitly.







Suppress C4267 "possible loss of data" warnings
2020-04-16T15:53:26+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2020-04-16T15:27:47+00:00

a0bc3f2a1c2c98f225612101cb4e1ea1a6813546












Warn on access/modify of $SAFE, and remove effects of modifying $SAFE
2019-11-17T23:00:25+00:00

Jeremy Evans
code@jeremyevans.net

2019-09-21T02:06:22+00:00

c5c05460ac20abcbc0ed686eb4acf06da7a39a79

This removes the security features added by $SAFE = 1, and warns for access
or modification of $SAFE from Ruby-level, as well as warning when calling
all public C functions related to $SAFE.

This modifies some internal functions that took a safe level argument
to no longer take the argument.

rb_require_safe now warns, rb_require_string has been added as a
version that takes a VALUE and does not warn.

One public C function that still takes a safe level argument and that
this doesn't warn for is rb_eval_cmd.  We may want to consider
adding an alternative method that does not take a safe level argument,
and warn for rb_eval_cmd.





This removes the security features added by $SAFE = 1, and warns for access
or modification of $SAFE from Ruby-level, as well as warning when calling
all public C functions related to $SAFE.

This modifies some internal functions that took a safe level argument
to no longer take the argument.

rb_require_safe now warns, rb_require_string has been added as a
version that takes a VALUE and does not warn.

One public C function that still takes a safe level argument and that
this doesn't warn for is rb_eval_cmd.  We may want to consider
adding an alternative method that does not take a safe level argument,
and warn for rb_eval_cmd.