search for: rb_str_new

Hi, What''s happening here? require ''windows/path'' require ''windows/unicode'' include Windows::Path include Windows::Unicode file_a = ''bar.txt'' file_w = multi_to_wide(file_a) p PathFindExtensionA(file_a) # ''.txt'' => OK p PathFindExtensionW(file_w) # ''.'' => WRONG Is Ruby chopping the

..././ext/digest -c digest.c digest.c: In function ''rb_digest_base_s_digest'': digest.c:100: warning: pointer targets in passing argument 2 of ''algo- >update_func'' differ in signedness digest.c:107: warning: pointer targets in passing argument 1 of ''rb_str_new'' differ in signedness digest.c: In function ''rb_digest_base_s_hexdigest'': digest.c:129: warning: pointer targets in passing argument 2 of ''algo- >update_func'' differ in signedness digest.c:136: warning: pointer targets in passing argument 1 of ...

--- configure.ac | 1 + ruby/run-ruby-tests | 27 --------------------------- ruby/run-ruby-tests.in | 27 +++++++++++++++++++++++++++ ruby/tests/tc_010_load.rb | 2 -- ruby/tests/tc_021_close.rb | 2 -- ruby/tests/tc_120_rlenvalue.rb | 4 +--- ruby/tests/tc_200_write.rb | 2 -- ruby/tests/tc_210_setvalue.rb | 2 -- run.in

Hi, David. I have recently fixed ferret C sources and successfully compile extension with MSVC.Net The problem was that MS compiler is more stricter that GCC and require that all variables were declared before using. There was ~30 such declaration. I have fixed them all. But I am not sure that it works because tests failed with following error both on clean and patched versions. So seems that it

Hi all, I''ve got overlapped and offset support in both nread and nwrite. The only thing left before I want to release this (as 0.4.0) is to get NO_BUFFERING to work. Unfortunately, I can''t get it to work. Park, I looked at that site you sent (and borrowed some code from it), but I don''t see anything special happening for NO_BUFFERING. I thought it required

...bxml2 -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0 -I. -I/usr/local/include -c ruby_xml_sax2_handler.c ruby_xml_sax2_handler.c: In function ‘end_element_ns_callback’: ruby_xml_sax2_handler.c:86: warning: pointer targets in passing argument 1 of ‘rb_str_new2’ differ in signedness ruby_xml_sax2_handler.c:88: warning: pointer targets in passing argument 2 of ‘rb_str_cat2’ differ in signedness ruby_xml_sax2_handler.c:92: warning: pointer targets in passing argument 1 of ‘rb_str_new2’ differ in signedness ruby_xml_sax2_handler.c:98: warning: pointer targe...

On Windows, there exist at least two APIs for dealing with the Registry: The Win32 API (RegCreateKeyA, RegCreateKeyW, etc.) works with null-terminated ASCII or UTF-16 strings. The native API (ZwCreateKey, etc.), on the other hand works with UTF-16 strings that are stored as buffers+length and may contain null characters. Malware authors have been relying on the Win32 API's inability to

...| RInt _ | RBool _ -> - pr " return INT2NUM (r);\n" + pr " return INT2NUM (r);\n" | RInt64 _ -> - pr " return ULL2NUM (r);\n" + pr " return ULL2NUM (r);\n" | RConstString _ -> - pr " return rb_str_new2 (r);\n"; + pr " return rb_str_new2 (r);\n"; | RConstOptString _ -> - pr " if (r)\n"; - pr " return rb_str_new2 (r);\n"; - pr " else\n"; - pr " return Qnil;\n"; + pr " if (r)\n"; +...