[rabbitmq-discuss] RabbitMQ.Net, Windows Powershell and CLS compliance
tonyg at lshift.net
Mon Mar 2 11:23:57 GMT 2009
Jon Palmer wrote:
> 2. Fixing the problem is a 'breaking change' in that it requires
> removing a public field. Its unlikely to be a big deal because the fix
> to use the property that is left is easy. However it might break some
> code that relies on the removed field.
The general rule for our code is: if it's on the implementation side
(RabbitMQ.Client.Impl namespace), then go wild. No code should be
relying on interfaces or implementations from the RabbitMQ.Client.Impl
namespaces -- none of it is public API.
Re potential other missed cases: it looks like in general, fields have
an "m_" prefix that the corresponding properties lack. If we are
consistent about it, it'll obviate the problem.
 Tony Garnock-Jones | Mob: +44 (0)7905 974 211
 LShift Ltd | Tel: +44 (0)20 7729 7060
  http://www.lshift.net/ | Email: tonyg at lshift.net
More information about the rabbitmq-discuss