- ...
(ESRF)1
- http://www.esrf.fr
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... II1.1
- http://www.frmii.de
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...
(HartRAO)1.2
- http://www.hartrao.ac.za
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... website1.3
- http://www.esrf.fr/computing/cs/taco
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...
server7.1
- ftp://ftp.esrf.fr/pub/cs/taco/taco_win32_v8_29.zip
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... server7.2
- ftp://ftp.esrf.fr/pub/cs/taco/dsapiNT/
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... 6.07.3
- /taco/oncrpc/win32/librpc/lib/oncrpc.dsw
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... !)9.1
- if agps_template was defined
as a new AGPowerSupply the first time the constructor is called
it will try to access agps_template->something but agps_template
does not exist yet and will generate a bus error
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... compiler9.2
- note that because the
GNU compiler uses a different algorithm for ``name mangling'' it
is not possible to mix GNU object files with those compiled with a
different compiler
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... separately10.1
-
One obvious way of doing this in OIC would have been to define two
partial structures - one called ClassPart which contains the fields
required by the method_finder
and one called DevServerClassPart which contains only the fields necessary
for the DevServerClass.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... structure10.2
- O
woe betide the device server programmer who has not understood pointers and
structures in C !
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... free()11.1
- this is a common source of memory
leaks in TACO clients
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... defined.11.2
- in the
past new types were added by device server programmer's as they
needed them; this led to a proliferation of exotic types which
was difficult to maintain and which needed to be implemented by
clients
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... TANGO11.3
- cf. http://www.esrf.fr/tango
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... file15.1
- ftp://ftp.esrf.fr/pub/cs/taco/lv_taco.zip
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... server.19.1
- each
copy of a device server has its own so-called ``personal name'' which
is used to identify, the full server name is therefore the name
of the executable followed by the personal name e.g. Newds/test
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.