Charm++ parallel programming system

["Van Der Wijngaart, Rob F" <rob.f.van.der.wijngaart AT intel.com>]

And here is another thing I ran into. It’s actually much less innocent than it seems.

Charmc doesn’t do the kind of type/syntax checking that a production compiler does. For example, I made some mistakes in the CkPrintf function (mismatch between I/O descriptor and type of variable being printed, or sometimes even a mismatch between the number of variables printed and the number of I/O descriptors). Charmc didn’t pick that up. So my code compiled just fine and I was merrily staring out the result of some print statements that made absolutely no sense. Could charmc start doing those checks as well? Thanks!

 

Rob

 

From: Van Der Wijngaart, Rob F
Sent: Friday, September 26, 2014 3:32 PM
To: 'Nikhil Jain'
Cc: Miller, Philip B; Kunzman, David M; Hammond, Jeff R; Mattson, Timothy G; charm AT cs.illinois.edu
Subject: Global variables in Charm++

 

Hello Nikhil,

 

I have a symbol that I define on the compile line (i.e. I stuff it in OPTS, as below):

OPTS=-DRADIUS=1

CHARMC=../../../bin/charmc $(OPTS)

When I now use RADIUS in my .C file, the C preprocessor does its work nicely and recognizes that I have defined RADIUS, and also what its value is. However, when I use RADIUS in the .ci file, charmc croaks. So is it true that no preprocessor is run on .ci files? Thanks!

 

Rob