Unlike other path resolution APIs, the resolveRelativePath function currently does not support being called with a NULL destination buffer pointer to return back a length.
Ideally it should support that behaviour.
Additionally whilst the resolveRelativePath function will check for NULL pointers for the input and output path buffers, this will not work when the mos_getabsolutepath API is called from Z80 mode code, as that currently blindly adjusts those pointers to include MB in the upper byte. This also should be fixed.
Unlike other path resolution APIs, the
resolveRelativePathfunction currently does not support being called with a NULL destination buffer pointer to return back a length.Ideally it should support that behaviour.
Additionally whilst the
resolveRelativePathfunction will check for NULL pointers for the input and output path buffers, this will not work when themos_getabsolutepathAPI is called from Z80 mode code, as that currently blindly adjusts those pointers to include MB in the upper byte. This also should be fixed.