Move the various map* functions to C; add #'map-into. src/ChangeLog addition: 2010-01-31 Aidan Kehoe <kehoea@parhasard.net> Move #'mapcar*, #'mapcan, #'mapc, #'map, #'mapl, #'mapcon to C; extend #'mapvector, #'mapconcat, #'mapcar to support more SEQUENCES; have them all error with circular lists. * fns.c (Fsubseq): Call CHECK_SEQUENCE here; Flength can return from the debugger if it errors with a non-sequence, leading to a crash in Fsubseq if sequence really is *not* a sequence. (mapcarX): Rename mapcar1 to mapcarX; rework it comprehensively to take an optional lisp output argument, and a varying number of sequences. Special-case a single list argument, as we used to, saving its elements in the stack space for the results before calling FUNCTION, so FUNCTION can corrupt the list all it wants. dead_wrong_type_argument() in the other cases if we encounter a non-cons where we expected a cons. (Fmapconcat): Accept further SEQUENCES after separator here. Special-case the idiom (mapconcat 'identity SEQUENCE), don't even funcall. (FmapcarX): Rename this from Fmapcar. Accept optional SEQUENCES. (Fmapvector): Accept optional SEQUENCES. (Fmapcan, Fmapc, Fmap): Move these here from cl-extra.el. (Fmap_into): New function, as specified by Common Lisp. (maplist): New function, the guts of the implementation of Fmaplist and Fmapl. (Fmaplist, Fmapl, Fmapcon): Move these from cl-extra.el. (syms_of_fns): Add a few needed symbols here, for the type tests used by #'map. Add the new subrs, with aliases for #'mapc-internal and #'mapcar. * general-slots.h: Declare Qcoerce here, now it's used in both indent.c and fns.c * indent.c (syms_of_indent): Qcoerce is gone from here. * lisp.h: Add ARRAYP(), SEQUENCEP(), and the corresponding CHECK_* macros. Declare Fbit_vector, Fstring, FmapcarX, now other files need to use them. * data.c (Farrayp, Fsequencep): Use ARRAYP and SEQUENCEP, just added to lisp.h * buffer.c (Fbuffer_list): Now Fmapcar has been renamed FmapcarX and takes MANY arguments, update this function to reflect that. lisp/ChangeLog addition: 2010-01-31 Aidan Kehoe <kehoea@parhasard.net> * cl.el (mapcar*): Delete; this is now in fns.c. Use #'mapc, not #'mapc-internal in a couple of places. * cl-macs.el (mapc, mapcar*, map): Delete these compiler macros now the corresponding functions are in fns.c; there's no run-time advantage to the macros. * cl-extra.el (coerce): Extend the possible conversions here a little; it's not remotely comprehensive yet, though it does allow running slightly more Common Lisp code than previously. (cl-mapcar-many): Delete. (map, maplist, mapc, mapl, mapcan, mapcon): Move these to fns.c. * bytecomp.el (byte-compile-maybe-mapc): Use #'mapc itself, not #'mapc-internal, now the former is in C. (mapcar*): Use #'byte-compile-maybe-mapc as this function's byte-compile method, now a #'mapc that can take more than one sequence is in C. * obsolete.el (cl-mapc): Move this compatibility alias to this file. * update-elc.el (do-autoload-commands): Use #'mapc, not #'mapc-internal here.

 * Sun May 3 1998 Oliver Graf <ograf@fga.de>

This path contains test code for the new XEmacs
Drag'n'Drop code.

To test the code do the following:
1) call 'bash droptest.sh' to create the test files in /tmp
2) load and eval droptest.el in XEmacs
3) Try to do some internal DnD by using the sources and targets
   in the new buffer
4) Do some external DnD:
   4a) CDE: use dtfile and dtpad
   4b) MSWindows: well, explorer should do. But only file data
                  should work, and I don't know if the test
                  already handles this.

The misc-user-event now also responds as a button-x-event
to the event-* query functions.

The function of a drag is called dragdrop-drop-dispatch
as you can see in droptest.el. From within the function
you can access the actual misc-user-event through the
current-mouse-event variable.

Short description of the object part of a drop misc-user-event:
( TYPE . DATA )
TYPE is either the symbol dragdrop_MIME
     or the symbol dragdrop_URL

DATA is a list of URL strings if TYPE is dragdrop_URL
     if TYPE is dragdrop_MIME DATA is either a string
     which contains the MIME data, or it is a list of
     ( CONTENT-TYPE CONTENT-ENCODING MIME-DATA )
     CONTENT-TYPE is encoded for tm-view (list, first element type,
	rest key.value conses)
     CONTENT-ENCODING is a string
     MIME-DATA is a string

     CONTENT-TYPE and -ENCODING can be directly supplied to mime/viewer-mode.