Can I just say "no" to this proposal?
Because:
- this proposal does not express the problem in detail.
- besides, C does not have any variable aliasing, C++ does.
- despite the observation in the proposal, the implementation would not be easy and simple at all. variables in Ruby is not implemented by memory links, but by binding in the table.
- this change may cause unexpected side-effect.
So I demand you to come back with why you really need this.
matz.
This is a cross-cutting concern, so it is an AOP-type feature. You may consider a more robust solution. A thread on suby-muse recently introduced the idea of sharable namespaces. For example:
namespace N
attr_accessor :x
end
class A
share N
end
class B
share N
end
a = A.new
b = B.new
a.x = 5
b.x # => 5
If you would be interested in flushing this out more, and help in improving your RCR, please join at:
http://lists.berlios.de/mailman/listinfo/suby-muse
The folks there are more than happy to discuss. ---
Can I just say "no" to this proposal?
Because:
So I demand you to come back with why you really need this.
matz.
This is a cross-cutting concern, so it is an AOP-type feature. You may consider a more robust solution. A thread on suby-muse recently introduced the idea of sharable namespaces. For example:
attr_accessor :x endclass A share N end
class B share N end
a = A.new b = B.new
a.x = 5 b.x # => 5
If you would be interested in flushing this out more, and help in improving your RCR, please join at:
The folks there are more than happy to discuss. ---