DSP Robotics Support

Hi,

I'm a little bit confused now. I'm looking for a way to define a constant in Ruby, that is only accessable in the RubyEdit it is defined in. Trying:


ended up, being readable in all RubyEdits. The only ways getting the results that I want, is using instance variables (but these would be overwriteable) or using a method that return the value for an input param. Is there another way, that I forgot?

Maik

Hi MyCo,
No, I don't think you've missed anything - constants are unique to a module or class namespace, but like classes and modules readable anywhere in the interpreter.
If you are looking to keep the value secure from overwrite, using a constant may not help anyway - Ruby allows constants to be overwritten; a warning is sent to STOUT, but no error is raised. In FS, even the STOUT warning doesn't appear.
Using an external value wouldn't help either, as the Ruby inputs can be written to using the input() method and by changing the @ins array contents - they are basically just instance variables.that happen to get overwritten by external inputs whenever a trigger arrives.
The only way I can think of would be to use a method that returns the value you want - if you need the initial value to be dynamic, the method definition could be within an eval that runs at the appropriate time, so long as the value can be turned into a parsable string...

Clunky, but I can't think of anything else to suggest.

I'm totally confused by the way Ruby works in FS. Thanks for the confirmation, this means I'm not a complete idiot

Here is another question. In the attached schematic, there is a sender, that sends out its RubyEdit (self) to wireless transmitter (and basically all other RubyEdits).
Is it safe to assume, that all RubyEdits are initialized, before they receive external Inputs from other components, even if they are RubyEdits? Or does it only work when the schematic is that simple like my example?

I'm working on a callback system... so there is one component, that receives "messages" from several other objects, and I want to be sure, that all "sender" objects receive the reference to the "callback" object.

I do not know if it can be useful, but in ruby ​​1.9.3 there is a feature freeze->obj.
a = [1]
a.freeze
.....
might work?

Tronic wrote:I do not know if it can be useful, but in ruby ​​1.9.3 there is a feature freeze->obj.
a = [1]
a.freeze
.....
might work?

For the constants problem? From the documentation it looks like this should lock the variable. But in FS, when I try it, I still can change the value. Don't know what's going on there

Here it work...

yeah, you can't change an object, but you can just re-assign it... doesn't make sense at all

I am using this method and it seems to work, simple and effective

that's the same way, that I've mentioned earlier, but why do you use self?

MyCo wrote:that's the same way, that I've mentioned earlier, but why do you use self?

simple but comprehensive answer here.