开发者

Should I consider memmove() O(n) or O(1)?

开发者 https://www.devze.com 2022-12-27 22:28 出处:网络
this may be a silly question, but I want to calculate the complexity of one of my algorithms, and I am not sure what complexity to consider for the memmove() function.

this may be a silly question, but I want to calculate the complexity of one of my algorithms, and I am not sure what complexity to consider for the memmove() function.

Can you please help / explain ?

void * memmove ( void * destination, const void开发者_如何学Go * source, size_t num );

So is the complexity O(num) or O(1). I suppose it's O(num), but I am not sure as I lack for now the understanding of what's going on under the hood.


Since the running time of memmove increases in direct proportionality with the number of bytes it is required to move, it is O(n).


What are you applying the memmove() operation to - selected elements in the algorithm or all of them? Are you applying memmove() to elements more than once?

Those are the things that will matter to the algorithm's complexity.

That answer may be different that the complexity of memmove() itself regarding the arrays of char elements that memmove() deals with (for which memmove() is an O(n) operation).

0

精彩评论

暂无评论...
验证码 换一张
取 消