"`map' is truncating" message and other assorted messages

Richard Fateman wrote:
>  
> 
> 
> Regarding map .. It seems that maperror:false should maybe have another
> option, maperror:quiet. 

I was thinking exactly the same thing.  But maybe maperror:quiet should 
still warn about this condition, mentioned in the docs:

(2) apply <f>
      to [<expr_1>, <expr_2>, ...] if the <expr_i> are not all the same
      type of object.

> 
> Set float2bf to false.  Maybe we should change the default now.

I think we should.  We should also fix the docs:

  -- Option variable: float2bf
      Default value: `false'

      When `float2bf' is `false', a warning message is printed when a
      floating point number is converted into a bigfloat number (since
      this may lead to loss of precision).

I don't think there is any loss of precision now.  And precision is 
probably the wrong word.  It should probably accuracy.

If there are no objections, I'll try to implement these.

Ray