>  On the other hand, what it comes down to is that the parser introduces a 
>  new type of global variable. Global variables are good or bad depending on 
>  how they are used. And in this case they come with a nice and controlled 
>  interface.  Ok, I vote in favour of allowing parameter resetting. 

Well I vote against it in general - I don't think people should reset a
parameter without printing a big screaming message to the screen. BAM is a
special case since there are special values of the grid sizes which are
required, but in general I think the approach we have been using to date
of not resetting parameters, but rather introducing defaults which we can
check for and react accordingly is the way to go.

So I would say official policy should be that noone should reset
parameters without thinking about it long and hard, and perhaps even
asking the powers-that-be (eg, cactus-maint). In this case it is obvious
it should occur, though.

>  While I am at it, I think I am going to add parameters nxyz and dxyz. Then 
>  do "if (nxyz) nx = ny = nz = nxyz;" after paramParse().  It is really 
>  minor but annoying to have to change three identical numbers for every 
>  other new parameter file. 

This is a great idea! Be sure to add it to cactus/src/include/param.h (eg,
the global parameters) rather than to some thorn.

	- Paul

>  PS: I already have absolution from PW, but does anybody else care to comment? 

Well, you had limited absolution...

Created for the WUGRAV CoCoBoard Page Projects Page.

Created by The CoCoBoard.