Subject: Discussion related to cado-nfs
List archive
- From: Paul Leyland <paul.leyland@gmail.com>
- To: Cado-nfs-discuss@lists.gforge.inria.fr
- Subject: [Cado-nfs-discuss] Possible enhancement?
- Date: Thu, 28 Nov 2013 17:50:18 +0000
- List-archive: <http://lists.gforge.inria.fr/pipermail/cado-nfs-discuss>
- List-id: A discussion list for Cado-NFS <cado-nfs-discuss.lists.gforge.inria.fr>
Now I'm getting more practice with V2.0 I find myself going through the
following procedure to set up a params file.
1) copy the prototype params.c1xy to a work directory
2) Delete a few lines from that copy
3) Copy some standard local boiler plate to set such things as the
network whitelist, number of cores per machine and so on.
4) Use diff to check that the new params file looks plausible.
Wouldn't It Be Nice If (tm) there was a #include mechanism for parameter
files? Each of the prototypes could then #include "local.params" to set
the local environment and overwrite / delete (i.e. overwrite with NULL)
inappropriate global variables.
Is it feasible to implement this WIBNI? Is there a better way of doing
the same thing at present than my laborious procedure?
Paul
- [Cado-nfs-discuss] Possible enhancement?, Paul Leyland, 11/28/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Zimmermann Paul, 11/28/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Paul Leyland, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Emmanuel Thomé, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Emmanuel Thomé, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Paul Leyland, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Zimmermann Paul, 11/28/2013
Archive powered by MHonArc 2.6.19+.