On Mon, 30 Sep 2002, DRYICE wrote:
> now available: > http://t2.technion.ac.il/~smeirm/lecture/lin_prog0.html > > please comment. on page 1, the 'why' - don't you want to mention the fact many of them need to deliver programs compiled under unix, and linux _is_ unix? on page 2 - just give a concrete example, such as: gcc file1.c file2.c file3.c -o progname it is clearer then using the '[]' constructs all over. you can put both these lines - first your '[]' line, then the line as it is actually written (and then better place it in italic font). on page 3 (gcc options): '-ansi' supports ANSI C, plus a few gnu extentions. '-pedantic' will disable those gnu extentions. at least this is what 'man gcc' sais. on pages with cut & paste - people would probably not know what 'yank' means. you should say that 'yank' is the same as 'paste'. on page with cutting words - i suggest to forget about cutting words. cutting lines is sufficient at the beginning, and very few will even remember the cut word option. leave them more space in their heads to remember searching - which is far more important. on page with file open/save - you generaly ignore the menus - people can open files and save them using the menus - show them that. they'll get back to the keybaord shortcuts after they 'settle in' with your beloved emacs ;) regarding compilation from within emacs - as i saw, the default compile command is 'make -k', which assumes you have a Makefile. can it be capled with a simple 'g++ -Wall file1.c file2.c -o prog' ? if so - you'll need to show them that. regarding search with C-s - you should show them how to do a 'search next' - it is very important (soemtimes you search for something that apears several times - nd you need to do a 'search next'). regarding gdb - gdb's built-in help is horrific. it _does_ have good 'info' pages (like gcc does). show them 'pinfo gdb' so they could learn on their own (i repeat 'pinfo', not 'info' - 'pinfo' is a useable program. 'info' is NOT). pressing 'next' from the 'gdb' slide does not work. in fact, all the links in the 'gdb' slide contian a directory path, rather then an http URL. in 'basic gdb commands' - write 'io' as 'I/O' - to make it more noticeable. in 'valgrind' - you have "valgrind is very easy use to use" should be "valgrind is very easy to use" also, please prepare a program with memory access errors, to demonstrate valgrind's use, like you did with 'testddd.c'. emphasize on valgrind, as its the one thing most students don't even know could exist, and can't easily get something similar for windows. in general, regarding anything - remember that people will not remember all the small details. its is important thus that you ocncentrate on what they _must_ know. in emacs - since one can move with arrows and page up/down keys, then the key combinations for movements are not mandatory - let them learn those later on, using the online tutorial. the days of terminals where these keys did not work properly - i think they are quite over. -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy -------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://linuxclub.il.eu.org) To unsub send an empty message to [EMAIL PROTECTED]
