Mercurial > hg > xemacs-beta
comparison src/lrecord.h @ 814:a634e3b7acc8
[xemacs-hg @ 2002-04-14 12:41:59 by ben]
latest changes
TODO.ben-mule-21-5: Update.
make-docfile.c: Add basic support for handling ISO 2022 doc strings -- we parse
the basic charset designation sequences so we know whether we're
in ASCII and have to pay attention to end quotes and such.
Reformat code according to coding standards.
abbrev.el: Add `global-abbrev-mode', which turns on or off abbrev-mode in all
buffers. Added `defining-abbrev-turns-on-abbrev-mode' -- if
non-nil, defining an abbrev through an interactive function will
automatically turn on abbrev-mode, either globally or locally
depending on the command. This is the "what you'd expect"
behavior.
indent.el: general function for indenting a balanced expression in a
mode-correct way. Works similar to indent-region in that a mode
can specify a specific command to do the whole operation; if not,
figure out the region using forward-sexp and indent each line
using indent-according-to-mode.
keydefs.el: Removed.
Modify M-C-backslash to do indent-region-or-balanced-expression.
Make S-Tab just insert a TAB char, like it's meant to do.
make-docfile.el: Now that we're using the call-process-in-lisp, we need to load
an extra file win32-native.el because we're running a bare temacs.
menubar-items.el: Totally redo the Cmds menu so that most used commands appear
directly on the menu and less used commands appear in submenus.
The old way may have been very pretty, but rather impractical.
process.el: Under Windows, don't ever use old-call-process-internal, even
in batch mode. We can do processes in batch mode.
subr.el: Someone recoded truncate-string-to-width, saying "the FSF version
is too complicated and does lots of hard-to-understand stuff" but
the resulting recoded version was *totally* wrong! it
misunderstood the basic point of this function, which is work in
*columns* not chars. i dumped ours and copied the version from
FSF 21.1. Also added truncate-string-with-continuation-dots,
since this idiom is used often.
config.inc.samp, xemacs.mak: Separate out debug and optimize flags.
Remove all vestiges of USE_MINIMAL_TAGBITS,
USE_INDEXED_LRECORD_IMPLEMENTATION, and GUNG_HO, since those
ifdefs have long been removed.
Make error-checking support actually work.
Some rearrangement of config.inc.samp to make it more logical.
Remove callproc.c and ntproc.c from xemacs.mak, no longer used.
Make pdump the default.
lisp.h: Add support for strong type-checking of Bytecount, Bytebpos,
Charcount, Charbpos, and others, by making them classes,
overloading the operators to provide integer-like operation and
carefully controlling what operations are allowed. Not currently
enabled in C++ builds because there are still a number of compile
errors, and it won't really work till we merge in my "8-bit-Mule"
workspace, in which I make use of the new types Charxpos,
Bytexpos, Memxpos, representing a "position" either in a buffer or
a string. (This is especially important in the extent code.)
abbrev.c, alloc.c, eval.c, buffer.c, buffer.h, editfns.c, fns.c, text.h: Warning fixes, some of them related to new C++ strict type
checking of Bytecount, Charbpos, etc.
dired.c: Caught an actual error due to strong type checking -- char len
being passed when should be byte len.
alloc.c, backtrace.h, bytecode.c, bytecode.h, eval.c, sysdep.c: Further optimize Ffuncall:
-- process arg list at compiled-function creation time, converting
into an array for extra-quick access at funcall time.
-- rewrite funcall_compiled_function to use it, and inline this
function.
-- change the order of check for magic stuff in
SPECBIND_FAST_UNSAFE to be faster.
-- move the check for need to garbage collect into the allocation
code, so only a single flag needs to be checked in funcall.
buffer.c, symbols.c: add debug funs to check on mule optimization info in buffers and
strings.
eval.c, emacs.c, text.c, regex.c, scrollbar-msw.c, search.c: Fix evil crashes due to eistrings not properly reinitialized under
pdump. Redo a bit some of the init routines; convert some
complex_vars_of() into simple vars_of(), because they didn't need
complex processing.
callproc.c, emacs.c, event-stream.c, nt.c, process.c, process.h, sysdep.c, sysdep.h, syssignal.h, syswindows.h, ntproc.c: Delete. Hallelujah, praise the Lord, there is no god
but Allah!!!
fix so that processes can be invoked in bare temacs -- thereby
eliminating any need for callproc.c. (currently only eliminated
under NT.) remove all crufty and unnecessary old process code in
ntproc.c and elsewhere. move non-callproc-specific stuff (mostly
environment) into process.c, so callproc.c can be left out under
NT.
console-tty.c, doc.c, file-coding.c, file-coding.h, lstream.c, lstream.h: fix doc string handling so it works with Japanese, etc docs.
change handling of "character mode" so callers don't have to
manually set it (quite error-prone).
event-msw.c: spacing fixes.
lread.c: eliminate unused crufty vintage-19 "FSF defun hack" code.
lrecord.h: improve pdump description docs.
buffer.c, ntheap.c, unexnt.c, win32.c, emacs.c: Mule-ize some unexec and startup code. It was pseudo-Mule-ized
before by simply always calling the ...A versions of functions,
but that won't cut it -- eventually we want to be able to run
properly even if XEmacs has been installed in a Japanese
directory. (The current problem is the timing of the loading of
the Unicode tables; this will eventually be fixed.) Go through and
fix various other places where the code was not Mule-clean.
Provide a function mswindows_get_module_file_name() to get our own
name without resort to PATH_MAX and such. Add a big comment in
main() about the problem with Unicode table load timing that I
just alluded to.
emacs.c: When error-checking is enabled (interpreted as "user is developing
XEmacs"), don't ask user to "pause to read messages" when a fatal
error has occurred, because it will wedge if we are in an inner
modal loop (typically when a menu is popped up) and make us unable
to get a useful stack trace in the debugger.
text.c: Correct update_entirely_ascii_p_flag to actually work.
lisp.h, symsinit.h: declarations for above changes.
author | ben |
---|---|
date | Sun, 14 Apr 2002 12:43:31 +0000 |
parents | a5954632b187 |
children | 6728e641994e |
comparison
equal
deleted
inserted
replaced
813:9541922fb765 | 814:a634e3b7acc8 |
---|---|
334 to describe every element, just the ones that need to be relocated, | 334 to describe every element, just the ones that need to be relocated, |
335 since the size of the lrecord is known. (The same goes for nested | 335 since the size of the lrecord is known. (The same goes for nested |
336 structures, whenever the structure size is given, rather than being | 336 structures, whenever the structure size is given, rather than being |
337 defaulted by specifying 0 for the size.) | 337 defaulted by specifying 0 for the size.) |
338 | 338 |
339 A struct_description is used for describing nested "structures". | 339 A struct_description is used for describing nested "structures". (Again |
340 (Again a misnomer, since it can be used for any blocks of memory, | 340 a misnomer, since it can be used for any blocks of memory, not just |
341 not just structures.) It just contains a size for the memory block, | 341 structures.) It just contains a size for the memory block, a pointer to |
342 a pointer to an lrecord_description, and (for unions only) a union | 342 an lrecord_description, and (for unions only) a union constant, |
343 constant, described below. The size can be 0 (#### not yet | 343 described below. The size can be 0, in which case the size will be |
344 implemented!), in which case the size will be determined from the | 344 determined from the largest offset logically referenced (i.e. last |
345 largest offset logically referenced (i.e. last offset mentioned + | 345 offset mentioned + size of that object). This is useful for stretchy |
346 size of that object). This is useful for stretchy arrays. | 346 arrays. |
347 | 347 |
348 Some example descriptions : | 348 Some example descriptions : |
349 | |
350 struct Lisp_String | |
351 { | |
352 struct lrecord_header lheader; | |
353 Bytecount size; | |
354 Intbyte *data; | |
355 Lisp_Object plist; | |
356 }; | |
349 | 357 |
350 static const struct lrecord_description cons_description[] = { | 358 static const struct lrecord_description cons_description[] = { |
351 { XD_LISP_OBJECT, offsetof (Lisp_Cons, car) }, | 359 { XD_LISP_OBJECT, offsetof (Lisp_Cons, car) }, |
352 { XD_LISP_OBJECT, offsetof (Lisp_Cons, cdr) }, | 360 { XD_LISP_OBJECT, offsetof (Lisp_Cons, cdr) }, |
353 { XD_END } | 361 { XD_END } |
354 }; | 362 }; |
355 | 363 |
356 Which means "two lisp objects starting at the 'car' and 'cdr' elements" | 364 Which means "two lisp objects starting at the 'car' and 'cdr' elements" |
357 | 365 |
358 static const struct lrecord_description string_description[] = { | 366 static const struct lrecord_description string_description[] = { |
359 { XD_BYTECOUNT, offsetof (Lisp_String, size) }, | 367 { XD_BYTECOUNT, offsetof (Lisp_String, size) }, |
360 { XD_OPAQUE_DATA_PTR, offsetof (Lisp_String, data), XD_INDIRECT(0, 1) }, | 368 { XD_OPAQUE_DATA_PTR, offsetof (Lisp_String, data), XD_INDIRECT(0, 1) }, |
361 { XD_LISP_OBJECT, offsetof (Lisp_String, plist) }, | 369 { XD_LISP_OBJECT, offsetof (Lisp_String, plist) }, |
362 { XD_END } | 370 { XD_END } |
363 }; | 371 }; |
364 "A pointer to string data at 'data', the size of the pointed array being the value | 372 |
365 of the size variable plus 1, and one lisp object at 'plist'" | 373 "A pointer to string data at 'data', the size of the pointed array being |
366 | 374 the value of the size variable plus 1, and one lisp object at 'plist'" |
367 The existing types : | 375 |
376 If your object has a pointer to an array of Lisp_Objects in it, something | |
377 like this: | |
378 | |
379 struct Lisp_Foo | |
380 { | |
381 ...; | |
382 int count; | |
383 Lisp_Object *objects; | |
384 ...; | |
385 } | |
386 | |
387 You'd use XD_STRUCT_PTR, something like: | |
388 | |
389 static const struct lrecord_description lo_description_1[] = { | |
390 { XD_LISP_OBJECT, 0 }, | |
391 { XD_END } | |
392 }; | |
393 | |
394 static const struct struct_description lo_description = { | |
395 sizeof (Lisp_Object), | |
396 lo_description_1 | |
397 }; | |
398 | |
399 static const struct lrecord_description foo_description[] = { | |
400 ... | |
401 { XD_INT, offsetof (Lisp_Foo, count) }, | |
402 { XD_STRUCT_PTR, offsetof (Lisp_Foo, objects), | |
403 XD_INDIRECT (0, 0), &lo_description }, | |
404 ... | |
405 }; | |
406 | |
407 | |
408 Another example of XD_STRUCT_PTR: | |
409 | |
410 typedef struct hentry | |
411 { | |
412 Lisp_Object key; | |
413 Lisp_Object value; | |
414 } hentry; | |
415 | |
416 struct Lisp_Hash_Table | |
417 { | |
418 struct lcrecord_header header; | |
419 Elemcount size; | |
420 Elemcount count; | |
421 Elemcount rehash_count; | |
422 double rehash_size; | |
423 double rehash_threshold; | |
424 Elemcount golden_ratio; | |
425 hash_table_hash_function_t hash_function; | |
426 hash_table_test_function_t test_function; | |
427 hentry *hentries; | |
428 enum hash_table_weakness weakness; | |
429 Lisp_Object next_weak; // Used to chain together all of the weak | |
430 // hash tables. Don't mark through this. | |
431 }; | |
432 | |
433 static const struct lrecord_description hentry_description_1[] = { | |
434 { XD_LISP_OBJECT, offsetof (hentry, key) }, | |
435 { XD_LISP_OBJECT, offsetof (hentry, value) }, | |
436 { XD_END } | |
437 }; | |
438 | |
439 static const struct struct_description hentry_description = { | |
440 sizeof (hentry), | |
441 hentry_description_1 | |
442 }; | |
443 | |
444 const struct lrecord_description hash_table_description[] = { | |
445 { XD_ELEMCOUNT, offsetof (Lisp_Hash_Table, size) }, | |
446 { XD_STRUCT_PTR, offsetof (Lisp_Hash_Table, hentries), XD_INDIRECT(0, 1), | |
447 &hentry_description }, | |
448 { XD_LO_LINK, offsetof (Lisp_Hash_Table, next_weak) }, | |
449 { XD_END } | |
450 }; | |
451 | |
452 Note that we don't need to declare all the elements in the structure, just | |
453 the ones that need to be relocated (Lisp_Objects and structures) or that | |
454 need to be referenced as counts for relocated objects. | |
455 | |
456 | |
457 The existing types : | |
458 | |
459 | |
368 XD_LISP_OBJECT | 460 XD_LISP_OBJECT |
369 A Lisp object. This is also the type to use for pointers to other lrecords. | 461 A Lisp object. This is also the type to use for pointers to other lrecords. |
370 | 462 |
371 XD_LISP_OBJECT_ARRAY | 463 XD_LISP_OBJECT_ARRAY |
372 An array of Lisp objects or (equivalently) pointers to lrecords. | 464 An array of Lisp objects or (equivalently) pointers to lrecords. |