Lines Matching defs:side
89 ;; when they are known to have no side-effects:
165 ;; ;; condition is side-effect-free [assignment-free] then the other
534 ((and for-effect (setq tmp (get fn 'side-effect-free))
1162 ;; (progn (list (something-with-side-effects) (yow))
1165 ;; (progn (progn (something-with-side-effects) (yow))
1169 ;; Some of these functions have the side effect of allocating memory
1182 (let ((side-effect-free-fns
1222 (side-effect-and-error-free-fns
1252 (while side-effect-free-fns
1253 (put (car side-effect-free-fns) 'side-effect-free t)
1254 (setq side-effect-free-fns (cdr side-effect-free-fns)))
1255 (while side-effect-and-error-free-fns
1256 (put (car side-effect-and-error-free-fns) 'side-effect-free 'error-free)
1257 (setq side-effect-and-error-free-fns (cdr side-effect-and-error-free-fns)))
1262 ;; pure functions are side-effect free functions whose values depend
1429 ;; How about other side-effect-free-ops? Is it safe to move an
1436 (defconst byte-compile-side-effect-and-error-free-ops
1444 (defconst byte-compile-side-effect-free-ops
1452 byte-compile-side-effect-and-error-free-ops))
1493 (side-effect-free (if byte-compile-delete-errors
1494 byte-compile-side-effect-free-ops
1495 byte-compile-side-effect-and-error-free-ops)))
1510 ;; <side-effect-free> pop --> <deleted>
1517 (memq (car lap0) side-effect-free))