Eric,
Why have the writeRaw and readRaw interfaces been removed? This
seems to
break the rule that we should always try and retain backwards
compatible
interfaces. I am already getting complaints that asynOctet devices we
support have broken. Doing this without a cast iron justification
seems
rather strange to me. I now have to maintain code that will compile
against multiple versions of asyn and so I need a number of horrible
ifdef's.
Cheers,
Nick Rees
Principal Software Engineer Phone: +44 (0)1235-778430
Diamond Light Source Fax: +44 (0)1235-446713
<DIV><FONT size="1" color="gray">This e-mail and any attachments may
contain confidential, copyright and or privileged material, and are
for the use of the intended addressee only. If you are not the
intended addressee or an authorised recipient of the addressee
please notify us of receipt by returning the e-mail and do not use,
copy, retain, distribute or disclose the information in or attached
to the e-mail.
Any opinions expressed within this e-mail are those of the
individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any
attachments are free from viruses and we cannot accept liability for
any damage which you may sustain as a result of software viruses
which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in
England and Wales with its registered office at Diamond House,
Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11
0DE, United Kingdom
</FONT></DIV>