RE: motor module compile problems

[Mark Rivers <rivers@cars.uchicago.edu>]

All of this code is C++.  In general it is recommended not to use NULL at all in C++, use 0 instead.  So I would suggest changing "(char) NULL" to "0".

Mark

-----Original Message-----
From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Jörn Dreyer
Sent: Wednesday, November 08, 2017 8:13 AM
To: tech-talk@aps.anl.gov
Subject: motor module compile problems

Hi,

I have had some trouble compiling the motor module (from git) on a openSuSE 
Tumbleweed system with gcc 7.2.1. It fails in all motor drivers at the calls 
of send_message where the last parameter is passed as (char) NULL. But in the 
definition of send_message the last parameter is defined as char*.
What would be the correct fix for this? One could
1. modify all calls to send_message(..,..,(char) NULL) to 
send_message(..,..,(char*) NULL), or
2. modify the definition of send_message(..,..,char*)to 
send_message(..,..,char), but then other calls may fail.

I chose  the first solution to get it compiled.  If needed I can send a patch 
file to correct all necessary lines.

Regards,

Jörn