Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!cbmehq!cbmita!digitm!steed
From: steed@digitm.UUCP (Steed Kulka)
Newsgroups: comp.sys.amiga.programmer
Subject: Demo versions
Message-ID: <00269.AA00269@digitm.UUCP>
Date: 21 Nov 91 19:39:20 GMT
Followup-To: comp.sys.amiga.programmer
Lines: 36


In article <91031.112859GHGAQA4@cc1.kuleuven.ac.be> GHGAQA4@cc1.kuleuven.ac.be
(Tyberghein Jorrit) writes:
>...
>I don't really know how to make a demo version of a debugger
>...

Make it suitable for 68000 only (i.e. do not include code ops for higher
cpus), disable log options, disable multitasking (breaking the Golden Rule
may be permitted in such cases, I guess), make demo executable only under
NOFASTMEM, enable small user-definable symbol tables. All things that leave
much of the original flavour, but don't make a demo a useful & friendly tool.

Do not compile routines which are not intended to be used in the demo.
We are currently giving away a demo/test version of our paint program Art
Nouveau which does not save pictures/clips/c-data/icons/patterns etc. - but
we did not include the actual code responsible for data saving, if we had
done such a foolness as:

	bra .this_is_a_demo
	...
	(saving routines here)
	...
this_is_a_demo:
	rest of proggie

hackers surely would have cracked it at once.

Good luck - we need good debuggers (sigh) ;-)
--
  _     _   _  ___ __        
 (_)   | \|/ _| | |_  /\ |\/|   Steed Kulka
-----  |_/|\_/| | |__/--\|  |

BIX: digiteam
UUCP: {uunet|pyramid|rutgers}!cbmvax!cbmehq!cbmita!digitm!steed