Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!milton.u.washington.edu!jsp From: jsp@glia.biostr.washington.edu (Jeff Prothero) Newsgroups: comp.lang.lisp.x Subject: xlftab.c:funtab[] & other questions Message-ID: Date: 19 Nov 90 23:46:28 GMT Sender: news@milton.u.washington.edu Distribution: comp Organization: Biological Structure, U of Wash, Seattle Lines: 23 Why are the xlftab.c:funtab[] entries so carefully numbered? What is going to break if the numbering is changed? Primarily the image save/restore stuff? Why can't/shouldn't those things which will break key off the function names instead of the table offsets? Why are extra slots reserved at the end of funtab[]? What's the point of image save/restore? Should saved images be portable between machines or versions? Would it be hard/pointless to write code to convert the xlisp state into initialized C header files, so that the xlisp state could be portably compiled into an application? {...YOYOYOY...:-} -- jsp@glia.biostr.washington.edu (Jeff Prothero) jsp@u.washington.edu (If above bounces.) Biological Structure Graphics Lab, U Washington