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, 2 deletions

diff --git a/src/TMaction.c b/src/TMaction.c
index 908ca61..fad1714 100644
--- a/src/TMaction.c
+++ b/src/TMaction.c
@@ -471,8 +471,7 @@ EnterBindCache(Widget w,
         }
         _XtGlobalTM.bindCacheTbl[_XtGlobalTM.numBindCache++] = bindCache;
 #endif                          /* TRACE_TM */
-        XtMemmove((XtPointer) &bindCache->procs[0],
-                  (XtPointer) procs, procsSize);
+        memcpy(&bindCache->procs[0], procs, procsSize);
     }
     UNLOCK_PROCESS;
     return &bindCache->procs[0];