[GRASS-dev] Re: [GRASS GIS] #1230: <suppress_required/> in r.out.gdal

[GRASS GIS]

#1230: <suppress_required/> in r.out.gdal
-------------------------+--------------------------------------------------
 Reporter:  rsbivand     |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  major        |   Milestone:  7.0.0                    
Component:  Raster       |     Version:  svn-trunk                
 Keywords:               |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by rsbivand):

 It may be permitted, but is much less obvious than

 <suppress_required>yes</suppress_required>
 <suppress_required>no</suppress_required>

 which is arguably more portable.

 r.in.gdal is affected by the same non-portability in flag "f".

 I have to work within the XML library linked by the XML R contributed
 package, so if that barfs, I'm stuck. One problem seems to be that
 <description> has typically always been the first component, but where
 <suppress_required> appears, it is now first. So some modules will
 optionally get an out-of-order component which, when present, means yes,
 and when absent means no? I guess I'm going to have to add code to loop
 through each flag entry checking the XML names, and set yes/no myself.

 Is the logic here that if I say "r.in.gdal -f", and if suppress_required
 is not set, one of the parameters may apply its required=YES value to
 terminate execution? Can flags with and without suppress_required set be
 mixed?

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1230#comment:2>
GRASS GIS <http://grass.osgeo.org>