[mkgmap-dev] splitter r247

Sat Dec 1 14:50:32 GMT 2012

> WanMil wrote
>> can you make the warning a bit more user friendly and add a hint, why
>> this usually is not a good idea to use overlap>0 in combination with
>> keep-complete=true?
>> I think people that doesn't follow the dev list won't have an easy
>> chance to find out why it is better to use overlap=0 with
>> keep-complete=true. And there are many old threads of the time before
>> keep-complete was introduced pointing out that overlap *must* be set.
>
> I agree. In fact I hate parameters that are mutual exclusive. Whenever
> possible we should try to
> avoid that. So what about this (written to stderr) ?
> Warning: --overlap is used in combination with --keep-complete=true
>           The option keep-complete should be used with overlap=0 because it
> is very unlikely that
>           the overlap will add any important data. It will just cause a lot
> of additional output which
>           has to be thrown away again in mkgmap.
>
>
> Gerd

Sounds good!

WanMil