[hatari-devel] Hatari options?

[Nicolas Pomarède]

Le 01/03/2011 20:56, Eero Tamminen a écrit :
> Attached patch would do that + put Laurent's additional WinAUE options
> under separate heading + re-order some other things more logically.
>
>
> 	- Eero
>


Hello,

I agree with adding most options you put, except :
	--cpu-exact
	--addr24  (typo : you put 42-bit mode in the man)

With WinUAE, there're many more modes than just cpu-exact : better 
prefetch, better exceptions, better cycle for micro code, so adding a 
bool option will not be enough.
Also we already have a "--compatible" option ; I think it would not be 
clear for the user what is the effect of "exact" compared to 
"compatible" (in theory, if the cpu emulation is "compatible" with real 
cpu, then it should be "exact").

I'd rather have a new parameter "--cpu-emulation" for example that could 
take several values : simple, cycle-precise, ...
Those are just some naming examples and it would encompass both 
--compatible and your --cpu-exact proposition ; but I think we should 
wait for a more advanced implementation of WinUAE core (that is having a 
working replacement for uae core in STF mode) before deciding on what 
values to add for this option.

Regarding --addr24, I'm not sure we have any real case for this now ; so 
better wait for above point to be solved and add both parameter at the 
same time.

I think it would be counter productive to add some options now, while we 
don't have enough "experience" on what will really be used in the end in 
WinUAE and the effect it can have on ST/Falcon emulation (it would be 
annoying to have some parameters in Hatari 1.5 for example, then notice 
in Hatari 1.6 that those parameters need to be changed ; not very good 
for the user to have changing parameters on each release)


Nicolas