Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!cernvax!chx400!chx400!bernina!neptune!iiic.ethz.ch!mneerach From: mneerach@iiic.ethz.ch (Matthias Ulrich Neeracher) Newsgroups: comp.sys.mac.programmer Subject: Re: Does anyone know anything about new Apple development products? Message-ID: <26592@neptune.inf.ethz.ch> Date: 4 Mar 91 19:53:33 GMT References: <1991Feb13.050326.24115@verity.com> <1991Feb13.215508.20111@ux1.cso.uiuc.edu> <25022@neptune.inf.ethz.ch> <1991Mar2.015219.8298@ux1.cso.uiuc.edu> Sender: news@neptune.inf.ethz.ch Reply-To: mneerach@iiic.ethz.ch Organization: Departement Informatik, ETH, Zurich Lines: 79 In article <1991Mar2.015219.8298@ux1.cso.uiuc.edu>, dorner@pequod.cso.uiuc.edu (Steve Dorner) writes: >Please tell me how to do the following things: Of course you are right, I can't do most of these things adequately either, but I had the impression I got used to most of it. >1. Use arbitrary expressions in the 'watch variable' window. I circumvent this by manually selectiong and executing lines in the worksheet. >2. See variable histories (like Watch Variable, but without erasing the old >values). See #1. >3. Use C syntax for structures and casts (trivial cases work, not complicated >ones). >4. Show me local variables UP the stack from the current context. (This >is the A#1 defect of SADE. Or do you like "Sorry, that variable is in >a register"?) >5. Show me argument lists on stack backtraces. >6. Let me decide what base I want numbers printed in. >7. Actually PRINT things in windows without doing a 'full stop': > break foo.(1) begin > bar > end > Doesn't print anything until a full break is encountered. Full breaks > engender major switches, screwing up window contents no end. I don't have a fix for any of these. Especially #6 annoys me very much, too. >8. set breaks by source line number (something I can ask my editor for) > rather than by executable statement number (which FORCES me to open > the file with SADE to discover). I can't do this, but I've never needed it. >9. Either save or don't save the 'junk' windows (worksheet, variable watch, > values); quit bugging me about them. I think I fixed this at least for the worksheet. Involves just changing the Quit script. >10. sc7 I berlieve I have something like this, but rarely need it. >I could probably fix 1 and 2, and maybe 9 and 10, if I wanted to spend a >few days debugging SADE scripts. 3-8 are just plain out, so far >as I can tell. (There may be more capabilities than I'm aware of, >since the manual is pretty, but superficial.) The scripts could use some work. I'm quite sure that 1,2,9,10 and probably even 8 could be fixed if Apple would provide some decent scripts with SADE (Apple... are you listening ?). 3 seems almost impossible in a multi language debugger. 4 seems to be very hard to do (Actually, it should be possible, but Apple probably doesn't want to copyleft SADE :-). 5,6 and 7 should be possible. >These are the things off the top of my head that drive me NUTS >about SADE. Even dbx (let alone gdb) can do most of them with a minimum >of pain. Am I all alone in wanting these things? Am I all alone in >thinking the SADE environment is kind of *weird*? It's a pity SADE can't do the simple things well, as it's quite good at the complicated ones. What I like about SADE is the mouse support and the scripting language; in terms of standard scripts and menus, SADE would make the Marquis feel proud. >-- >Steve Dorner, U of Illinois Computing Services Office >Internet: s-dorner@uiuc.edu UUCP: uunet!uiucuxc!uiuc.edu!s-dorner Matthias -- Matthias Neeracher mneerach@iiic.ethz.ch "These days, though, you have to be pretty technical before you can even aspire to crudeness." -- William Gibson, _Johnny Mnemonic_