Problems with rb_str_split()

ruby-talk
1

Ian Macdonald wrote:

This can probably be fixed with this:

cap_list = rb_str_split(rb_reg_new(txt, strlen(txt), 0), comma_sp);

but this is entirely untested. Do you want to give it a try?

OK, so that doesn’t work. I know what the problem is, but I don’t know
how to fix it.

You’re way ahead of me… I’m not sure I even understand the problem.
:frowning:

I have a piece of code that look like this:

const char *comma_sp = ", ";

cap_list = rb_str_split(rb_str_new2(txt), comma_sp);

This worked fine in Ruby 1.6.x, but in 1.8.x, it generates a warning in
any code that invokes the method:

/usr/bin/mycal:101: warning: string pattern instead of regexp; metacharacters no longer effective

Now, I understand why this happens and I’m quite capable of fixing the
same error when it occurs in pure Ruby code, but I can’t seem to figure
out how to fix it in Ruby C.

The prototype from intern.h looks like this:

VALUE rb_str_split _((VALUE, const char*));

So, what’s the problem? How do I pass rb_str_split a regex as its second
argument, instead of a string?

I thought the answer might be this:

cap_list = rb_str_split(rb_str_new2(txt),
rb_reg_new(comma_sp,
strlen(comma_sp), 0));

but that makes a VALUE out of the second argument, which is not what the
prototype expects, so a warning is issued during compilation.

Any ideas?

Ian

···

On Wed 29 Oct 2003 at 17:06:07 -0500, Ian Macdonald wrote:
–
Ian Macdonald | Ashes to ashes, dust to dust, If God won’t
System Administrator | have you, the devil must.
ian@caliban.org |
http://www.caliban.org |

2

This worked fine in Ruby 1.6.x, but in 1.8.x, it generates a warning in
any code that invokes the method:

Well, I don't have this problem with 1.8.1

nasun% cat aa.c
#include <ruby.h>

void Init_aa()
{
    VALUE res;
    const char *comma_sp = ", ";
    int i;

    res = rb_str_split(rb_str_new2("abc, def"), ", ");
    for (i = 0; i < RARRAY(res)->len; i++) {
        rb_warn("found %s", StringValuePtr(RARRAY(res)->ptr[i]));
    }
}
nasun%

nasun% ruby -raa -ve 1
ruby 1.8.1 (2003-10-31) [sparc-solaris2.8]
./aa.so: warning: found abc
./aa.so: warning: found def
-e:1: warning: useless use of a literal in void context
nasun%

Guy Decoux

3

Try running it with warnings enabled (-w):

[ianmacd@jiskefet]$ ruby -raa -wve 1
ruby 1.8.0 (2003-08-04) [i686-linux-gnu]
./aa.so: warning: string pattern instead of regexp; metacharacters no longer effective
./aa.so: warning: found abc
./aa.so: warning: found def
-e:1: warning: useless use of a literal in void context

So, how do I get rid of the “string pattern instead of regexp” warning?

Ian

···

On Wed 12 Nov 2003 at 20:02:33 +0900, ts wrote:

This worked fine in Ruby 1.6.x, but in 1.8.x, it generates a warning in
any code that invokes the method:

Well, I don’t have this problem with 1.8.1

nasun% cat aa.c
#include <ruby.h>

void Init_aa()
{
VALUE res;
const char *comma_sp = ", ";
int i;

res = rb_str_split(rb_str_new2("abc, def"), ", ");
for (i = 0; i < RARRAY(res)->len; i++) {
    rb_warn("found %s", StringValuePtr(RARRAY(res)->ptr[i]));
}

}
nasun%

nasun% ruby -raa -ve 1
ruby 1.8.1 (2003-10-31) [sparc-solaris2.8]
./aa.so: warning: found abc
./aa.so: warning: found def
-e:1: warning: useless use of a literal in void context
nasun%

–
Ian Macdonald | A is for Apple. – Hester Pryne
System Administrator |
ian@caliban.org |
http://www.caliban.org |
>

4

Well, I don't have this problem with 1.8.1

         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Try running it with warnings enabled (-w):

With -v warning are enabled

[ianmacd@jiskefet]$ ruby -raa -wve 1
ruby 1.8.0 (2003-08-04) [i686-linux-gnu]

nasun% ruby -raa -wve 1
ruby 1.8.1 (2003-10-31) [sparc-solaris2.8]
./aa.so: warning: found abc
./aa.so: warning: found def
-e:1: warning: useless use of a literal in void context
nasun%

Guy Decoux

···

On Wed 12 Nov 2003 at 20:02:33 +0900, ts wrote:

5

So, it was just a bug in 1.8.0? Unfortunately, that’s still the latest
official version, so I’m stuck with the issue at work for the time
being.

Thanks for your reply.

Ian

···

On Thu 13 Nov 2003 at 18:17:27 +0900, ts wrote:

On Wed 12 Nov 2003 at 20:02:33 +0900, ts wrote:

Well, I don’t have this problem with 1.8.1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try running it with warnings enabled (-w):

With -v warning are enabled

[ianmacd@jiskefet]$ ruby -raa -wve 1
ruby 1.8.0 (2003-08-04) [i686-linux-gnu]

nasun% ruby -raa -wve 1
ruby 1.8.1 (2003-10-31) [sparc-solaris2.8]
./aa.so: warning: found abc
./aa.so: warning: found def
-e:1: warning: useless use of a literal in void context
nasun%

–
Ian Macdonald | Fifth Law of Procrastination:
System Administrator | Procrastination avoids boredom; one never
ian@caliban.org | has the feeling that there is nothing
http://www.caliban.org | important to do.
>

6

Has anyone compiled ruby with bcc32 under a windows environment( preferably
win2000 ) successfully?

I’m having troubles.

Zach

···

-----Original Message-----
From: Ian Macdonald [mailto:ian@caliban.org]
Sent: Thursday, November 13, 2003 5:29 AM
To: ruby-talk ML
Subject: Re: problems with rb_str_split()

On Thu 13 Nov 2003 at 18:17:27 +0900, ts wrote:

On Wed 12 Nov 2003 at 20:02:33 +0900, ts wrote:

Well, I don’t have this problem with 1.8.1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try running it with warnings enabled (-w):

With -v warning are enabled

[ianmacd@jiskefet]$ ruby -raa -wve 1
ruby 1.8.0 (2003-08-04) [i686-linux-gnu]

nasun% ruby -raa -wve 1
ruby 1.8.1 (2003-10-31) [sparc-solaris2.8]
./aa.so: warning: found abc
./aa.so: warning: found def
-e:1: warning: useless use of a literal in void context
nasun%

So, it was just a bug in 1.8.0? Unfortunately, that’s still the latest
official version, so I’m stuck with the issue at work for the time
being.

Thanks for your reply.

Ian

Ian Macdonald | Fifth Law of Procrastination:
System Administrator | Procrastination avoids boredom; one never
ian@caliban.org | has the feeling that there is nothing
http://www.caliban.org | important to do.
>

7

So, it was just a bug in 1.8.0? Unfortunately, that's still the latest
official version, so I'm stuck with the issue at work for the time
being.

svg% diff -u aa.c~ aa.c
--- aa.c~ 2003-11-13 11:34:19.000000000 +0100
+++ aa.c 2003-11-13 11:37:33.000000000 +0100
@@ -2,11 +2,14 @@

void Init_aa()
{
- VALUE res;
+ VALUE res, rv;
     const char *comma_sp = ", ";
     int i;

+ rv = ruby_verbose;
+ ruby_verbose = Qnil;
     res = rb_str_split(rb_str_new2("abc, def"), ", ");
+ ruby_verbose = rv;
     for (i = 0; i < RARRAY(res)->len; i++) {
         rb_warn("found %s", StringValuePtr(RARRAY(res)->ptr[i]));
     }
svg%

svg% ruby -raa -vwe 1
ruby 1.8.0 (2003-08-04) [i686-linux]
./aa.so: warning: found abc
./aa.so: warning: found def
-e:1: warning: useless use of a literal in void context
svg%

Guy Decoux

8

That’s a nice way around the problem.

Thanks!

Ian

···

On Thu 13 Nov 2003 at 19:39:20 +0900, ts wrote:

So, it was just a bug in 1.8.0? Unfortunately, that’s still the latest
official version, so I’m stuck with the issue at work for the time
being.

svg% diff -u aa.c~ aa.c
— aa.c~ 2003-11-13 11:34:19.000000000 +0100
+++ aa.c 2003-11-13 11:37:33.000000000 +0100
@@ -2,11 +2,14 @@

void Init_aa()
{

  • VALUE res;

  • VALUE res, rv;
    const char *comma_sp = ", ";
    int i;

  • rv = ruby_verbose;

  • ruby_verbose = Qnil;
    res = rb_str_split(rb_str_new2(“abc, def”), ", ");

  • ruby_verbose = rv;
    for (i = 0; i < RARRAY(res)->len; i++) {
    rb_warn(“found %s”, StringValuePtr(RARRAY(res)->ptr[i]));
    }

–
Ian Macdonald | Actually, what I’d like is a little toy
System Administrator | spaceship!!
ian@caliban.org |
http://www.caliban.org |
>

9

Zach Dennis wrote:

Has anyone compiled ruby with bcc32 under a windows environment( preferably
win2000 ) successfully?

I’m having troubles.

Zach,

I compiled it with no trouble by following the steps in readme.bcc32 in
the bcc32 folder–both under Win2K and WinXP. Start a console. Be sure
you are in the “Ruby-1.8.1” directory. Then, set your path to include
both bin & the lib of bcc
(path=%path%;c:\borland\bcc55\bin;c:\borland\bcc55\bib) and just follow
the remaining steps.

It worked, and I was able to run basic Ruby programs successfully.
However, what keeps me using Andy’s Win32 install is all the little
extras! Even though I can compile with bcc, I have no clue how to
compile all the great *.so file (like Oracle) that make Ruby such a
valuable tool for me.

Also, there’s a unique item with bcc32. When you read a file, you must
be sure to include the binary flag “b” or you’ll have trouble with
stripping characters–IIRC, lone CR’s in mac files on my Win box.

(Now, if I only had a 4D plug-in to run Ruby in that environment!)

···

–
Regards,

Mark Smith
maslists [at] cox [dot] net

10

That's a nice way around the problem.

You can still use

    res = rb_funcall(rb_str_new2("abc, def"), rb_intern("split"),
         1, rb_reg_new(", ", 2, 0));

Guy Decoux

11

Mark,

You use 4d to? I didn’t think there were any other Ruby’ers out there who
used it! Maybe we shall have to write some 4D-extensions for Ruby. =)

Zach

···

-----Original Message-----
From: Mark Smith [mailto:spam@fakeaddress.net]
Sent: Sunday, November 16, 2003 9:07 PM
To: ruby-talk ML
Subject: Re: BCC32 under win environment

Zach Dennis wrote:

Has anyone compiled ruby with bcc32 under a windows environment(
preferably
win2000 ) successfully?

I’m having troubles.

Zach,

I compiled it with no trouble by following the steps in readme.bcc32 in
the bcc32 folder–both under Win2K and WinXP. Start a console. Be sure
you are in the “Ruby-1.8.1” directory. Then, set your path to include
both bin & the lib of bcc
(path=%path%;c:\borland\bcc55\bin;c:\borland\bcc55\bib) and just follow
the remaining steps.

It worked, and I was able to run basic Ruby programs successfully.
However, what keeps me using Andy’s Win32 install is all the little
extras! Even though I can compile with bcc, I have no clue how to
compile all the great *.so file (like Oracle) that make Ruby such a
valuable tool for me.

Also, there’s a unique item with bcc32. When you read a file, you must
be sure to include the binary flag “b” or you’ll have trouble with
stripping characters–IIRC, lone CR’s in mac files on my Win box.

(Now, if I only had a 4D plug-in to run Ruby in that environment!)

–
Regards,

Mark Smith
maslists [at] cox [dot] net