[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

RubyInline

R. Mark Volkmann

3/2/2007 5:19:00 PM

I'm using RubyInline-3.6.2 and am having trouble getting this simple
example to work.

require 'rubygems'
require 'inline'

class Example
inline do |builder|
builder.c "
int simple() {
int x = 10;
return x;
}"
end
end

p Example.new.simple

When I run this I get

/usr/local/lib/ruby/gems/1.8/gems/RubyInline-3.6.2/./inline.rb:378:in
`build': undefined method `+' for nil:NilClass (NoMethodError)
from /usr/local/lib/ruby/gems/1.8/gems/RubyInline-3.6.2/./
inline.rb:628:in `inline'
from demo.rb:5

I'm not sure if I'm doing something wrong or there is a bug in that
version of RubyInline.
17 Answers

Ryan Davis

3/2/2007 7:29:00 PM

0


On Mar 2, 2007, at 9:18 AM, Mark Volkmann wrote:

> I'm using RubyInline-3.6.2 and am having trouble getting this
> simple example to work.
>
> require 'rubygems'
> require 'inline'
>
> class Example
> inline do |builder|
> builder.c "
> int simple() {
> int x = 10;
> return x;
> }"
> end
> end
>
> p Example.new.simple
>
> When I run this I get
>
> /usr/local/lib/ruby/gems/1.8/gems/RubyInline-3.6.2/./inline.rb:
> 378:in `build': undefined method `+' for nil:NilClass (NoMethodError)
> from /usr/local/lib/ruby/gems/1.8/gems/RubyInline-3.6.2/./
> inline.rb:628:in `inline'
> from demo.rb:5
>
> I'm not sure if I'm doing something wrong or there is a bug in that
> version of RubyInline.

First off, this isn't the right forum for reporting something like
this. Filing a bug on the rubyinline project on rubyforge is the
correct forum.

That said, No bug has been reported against this version of inline.

Please provide output of the following:

ruby -v -rrbconfig -e 'p Config::CONFIG["archdir"], Config::CONFIG
["srcdir"]'

Gregory Brown

3/2/2007 7:35:00 PM

0

On 3/2/07, Ryan Davis <ryand-ruby@zenspider.com> wrote:

> First off, this isn't the right forum for reporting something like
> this. Filing a bug on the rubyinline project on rubyforge is the
> correct forum.

This is starting to be a real problem, in the sense that bug reports
or problems end up in RubyTalk or some other forum / mailing list
rather than in the hands of the developers who can address the
problems in the format they expect.

With no offense intended to the OP, how can we get people to go to the
right place?
For example, Ruport we want you to use our Trac and/or Mailing List
for contact, but putting these links in our README doesn't seem to do
the trick.

I'm mostly looking for ideas, but how do you guys think we can best
direct traffic? Maybe hacking a "where to go for help" link into
RubyForge?

Joel VanderWerf

3/2/2007 8:10:00 PM

0

Gregory Brown wrote:
> On 3/2/07, Ryan Davis <ryand-ruby@zenspider.com> wrote:
>
>> First off, this isn't the right forum for reporting something like
>> this. Filing a bug on the rubyinline project on rubyforge is the
>> correct forum.
>
> This is starting to be a real problem, in the sense that bug reports
> or problems end up in RubyTalk or some other forum / mailing list
> rather than in the hands of the developers who can address the
> problems in the format they expect.
>
> With no offense intended to the OP, how can we get people to go to the
> right place?
> For example, Ruport we want you to use our Trac and/or Mailing List
> for contact, but putting these links in our README doesn't seem to do
> the trick.
>
> I'm mostly looking for ideas, but how do you guys think we can best
> direct traffic? Maybe hacking a "where to go for help" link into
> RubyForge?

Is this really a problem?

If it's not a bug, asking on ruby-talk may be the best way to get help.

--
vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407

Gregory Brown

3/2/2007 8:30:00 PM

0

On 3/2/07, Joel VanderWerf <vjoel@path.berkeley.edu> wrote:

> > I'm mostly looking for ideas, but how do you guys think we can best
> > direct traffic? Maybe hacking a "where to go for help" link into
> > RubyForge?
>
> Is this really a problem?
>
> If it's not a bug, asking on ruby-talk may be the best way to get help.

I just feel like the best help you can hope to get on projects is from
the authors of those projects or the users who've managed to find the
communication channels closer to the project.

RubyTalk is no longer at a traffic level in which it can comfortably
support discussions about specific projects, unless they're somewhat
general, I feel.

Even if that's not an issue, I guess I just favour archive
preservation somewhere closer to the actual project.

Just an opinion of course, and RubyTalk is a great place to go when
you can't find the right place, if nothing else, to be pointed in the
right direction.

Eric Hodel

3/2/2007 8:59:00 PM

0

On Mar 2, 2007, at 12:09, Joel VanderWerf wrote:
> Gregory Brown wrote:
>> On 3/2/07, Ryan Davis <ryand-ruby@zenspider.com> wrote:
>>> First off, this isn't the right forum for reporting something like
>>> this. Filing a bug on the rubyinline project on rubyforge is the
>>> correct forum.
>> This is starting to be a real problem, in the sense that bug reports
>> or problems end up in RubyTalk or some other forum / mailing list
>> rather than in the hands of the developers who can address the
>> problems in the format they expect.
>> With no offense intended to the OP, how can we get people to go to
>> the
>> right place?
>> For example, Ruport we want you to use our Trac and/or Mailing List
>> for contact, but putting these links in our README doesn't seem to do
>> the trick.
>> I'm mostly looking for ideas, but how do you guys think we can best
>> direct traffic? Maybe hacking a "where to go for help" link into
>> RubyForge?
>
> Is this really a problem?

Yes. For example, for RubyGems there are many bug reports here (and
on the RubyGems list) that should be in the tracker. The active
RubyGems developers don't have the time to read ruby-talk, so these
bug reports are just going to get lost.

> If it's not a bug, asking on ruby-talk may be the best way to get
> help.

If you're doing something and there's an exception, its probably a bug.

R. Mark Volkmann

3/2/2007 9:11:00 PM

0

On Mar 2, 2007, at 1:28 PM, Ryan Davis wrote:

>
> On Mar 2, 2007, at 9:18 AM, Mark Volkmann wrote:
>
>> I'm using RubyInline-3.6.2 and am having trouble getting this
>> simple example to work.
>>
>> require 'rubygems'
>> require 'inline'
>>
>> class Example
>> inline do |builder|
>> builder.c "
>> int simple() {
>> int x = 10;
>> return x;
>> }"
>> end
>> end
>>
>> p Example.new.simple
>>
>> When I run this I get
>>
>> /usr/local/lib/ruby/gems/1.8/gems/RubyInline-3.6.2/./inline.rb:
>> 378:in `build': undefined method `+' for nil:NilClass (NoMethodError)
>> from /usr/local/lib/ruby/gems/1.8/gems/RubyInline-3.6.2/./
>> inline.rb:628:in `inline'
>> from demo.rb:5
>>
>> I'm not sure if I'm doing something wrong or there is a bug in
>> that version of RubyInline.
>
> First off, this isn't the right forum for reporting something like
> this. Filing a bug on the rubyinline project on rubyforge is the
> correct forum.

I'll admit to why I did this. It's probably the reason you would
guess. I was perhaps being a little lazy. It's cumbersome to have to
sign up for the mailing list of every Ruby library if you don't
anticipate needing to use them very much. I just wanted to try out
RubyInline. I was hoping that I could get a quick answer without
having to signup for another mailing list, post there, wait for an
answer, and unsubscribe. I thought I could sneak that through since
there was an announcement about RubyInline on this list. I understand
your concern though, so I'll sign up and ask my question on that list.

Ara.T.Howard

3/2/2007 9:31:00 PM

0

Ryan Davis

3/2/2007 10:06:00 PM

0


On Mar 2, 2007, at 1:11 PM, Mark Volkmann wrote:

> I'll admit to why I did this. It's probably the reason you would
> guess. I was perhaps being a little lazy. It's cumbersome to have
> to sign up for the mailing list of every Ruby library if you don't
> anticipate needing to use them very much. I just wanted to try out
> RubyInline. I was hoping that I could get a quick answer without
> having to signup for another mailing list, post there, wait for an
> answer, and unsubscribe. I thought I could sneak that through since
> there was an announcement about RubyInline on this list. I
> understand your concern though, so I'll sign up and ask my question
> on that list.

Filing a bug != subscribe to mailing list.

My whole point was that mailing lists are fleeting and not even
remotely guaranteed to be tracked over time. That is why we have bug
dbs in the first place.

Ryan Davis

3/2/2007 10:09:00 PM

0


On Mar 2, 2007, at 11:35 AM, Gregory Brown wrote:

> On 3/2/07, Ryan Davis <ryand-ruby@zenspider.com> wrote:
>
>> First off, this isn't the right forum for reporting something like
>> this. Filing a bug on the rubyinline project on rubyforge is the
>> correct forum.
>
> This is starting to be a real problem, in the sense that bug reports
> or problems end up in RubyTalk or some other forum / mailing list
> rather than in the hands of the developers who can address the
> problems in the format they expect.

Gregory, I couldn't agree more. I've missed a number of things
because they get sent here.

> I'm mostly looking for ideas, but how do you guys think we can best
> direct traffic? Maybe hacking a "where to go for help" link into
> RubyForge?

I'm still not sure. I thought that adding urls on all my readmes,
email announcements, blog announcements would be enough, but
obviously it isn't. I think at some stage I have to say that I did
_my_ due diligence and now it is on the user to do theirs, but
obviously, that means that potentially important stuff will slip
through.

Joel VanderWerf

3/2/2007 10:26:00 PM

0

Ryan Davis wrote:
>
> On Mar 2, 2007, at 1:11 PM, Mark Volkmann wrote:
>
>> I'll admit to why I did this. It's probably the reason you would
>> guess. I was perhaps being a little lazy. It's cumbersome to have to
>> sign up for the mailing list of every Ruby library if you don't
>> anticipate needing to use them very much. I just wanted to try out
>> RubyInline. I was hoping that I could get a quick answer without
>> having to signup for another mailing list, post there, wait for an
>> answer, and unsubscribe. I thought I could sneak that through since
>> there was an announcement about RubyInline on this list. I understand
>> your concern though, so I'll sign up and ask my question on that list.
>
> Filing a bug != subscribe to mailing list.
>
> My whole point was that mailing lists are fleeting and not even remotely
> guaranteed to be tracked over time. That is why we have bug dbs in the
> first place.
>

I guess my point is that people file bugs that aren't. Every now and
then the ruby-core list gets a generated copy of a bug report saying
something like "I don't like how feature X behaves", typically something
answered in the FAQ and in ruby-talk archives. For example:

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-...

At least in the case of ruby itself, it seems better to filter this kind
of thing through ruby-talk before it escalates to bother the developers.

Also, I like to learn about other projects without having to subscribe
to all their lists....

I do agree that in the case of real bugs, you want to find the reports
in your db, rather than have to read every message on ruby-talk. So, I
guess there's a tradeoff...

--
vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407