Having good names for arguments can really help or hinder and API. Rather than one argument that tries to do two different things, which makes it hard to describe or use properly, splitting it into two that are easy to name seems to be the way to go.Stef wrote:Finally the good name for these argumentsChilly Willy wrote: Leave the current function alone and make a new one that takes a separate arguments for flags and tileoffset.
I think i should replace "basetile" by "flags" on the previous method and add a new as you said.
As to keeping old functions, that should be partly based on how much uses it, how easy it is to convert to the new function, and whether keeping the old function may confuse people. Perhaps a define for the old function that converts to the new one is better. Perhaps a compile warning that the function is outdated and a new one is available. There's a number of options here.