Use memcpy() instead of XtMemmove() when buffers are known to differ

Most of these came from a mass XtBCopy() -> XtMemmove() substitution
in 1993 with a commit comment of "ANSIfication".

But include/X11/IntrinsicI.h now defines XtMemmmove() as just
calling memcpy() as long as src & dst differ, so remove an
unnecessary check when we've just allocated a buffer, and reduce
the chance that someone thinks we'll actually call memmove() instead
of memcpy()

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/src/Resources.c b/src/Resources.c
index d8ea4fc..15a78c2 100644
--- a/src/Resources.c
+++ b/src/Resources.c
@@ -377,7 +377,7 @@ _XtDependencies(XtResourceList *class_resp,    /* VAR */
     new_res = (XrmResourceList *)
         __XtMalloc((Cardinal) (new_num_res * sizeof(XrmResourceList)));
     if (super_num_res > 0)
-        XtMemmove(new_res, super_res, super_num_res * sizeof(XrmResourceList));
+        memcpy(new_res, super_res, super_num_res * sizeof(XrmResourceList));
 
     /* Put pointers to class resource entries into new_res */
     new_next = super_num_res;