Steven R. Brandt

@ct-clmsn one can, in principle do what you propose with annotate_d(), I believe. It's a question of level of user friendliness.

@hkaiser yes, it does.

Rewriting the code as follows: ``` from phylanx import Phylanx, PhylanxSession cfg = [ # make sure hpx_main is always executed "hpx.run_hpx_main!=1", # allow for unknown command line options "hpx.commandline.allow_unknown!=1",...

@hkaiser this setting has no effect. :(

As of this commit ``` commit e89bb10f6aa2e75227e7ba05902b7ea9c93320a1 Author: Mikael Simberg Date: Wed Feb 19 17:04:14 2020 +0100 ``` it's still not working.

@hkaiser Note that ``` ./build.Release/bin/physl --hpx:hpx=127.0.0.1:7909 --connect ``` Also exits instantly. Somehow, the hpx arguments are not compatible with the physl arguments. Not sure why.

@hkaiser the connect option was something I added for the PR, so that I could call finalize instead of disconnect, etc.

I now see that the modification to physl wasn't needed, the option `--hpx:connect` does it.

OK, I can connect localities, but I cannot use them. So I have a main process which waits for 4 localties, then tries to run a cannon product (which requires...

@hkaiser I also attempted to have all localities run the same code, i.e. `can.p`. The all print `cannon!` and then all hang.