Re: 0.25k Programming Contest!

[sheldon@netcom.com (Sheldon Simms)]

In article <3lmgpq$k5q@cville-srv.wam.umd.edu> iigs@wam.umd.edu (Geoff Weiss - The Doctor) writes:

>I'm hoping some of these rules can be extended since now only two
>people publically stated what some of the rules should be.

Well that's true, by concensus I also meant that no one had disagreed - yet.

>>(2) Must run on an enhanced, 128k Apple //e.
>
>IIgs specific programs are being excluded from this.  I was hoping
>to write a 256 byte IIgs specific program :).  

My only problem with this is how can there be a fair judgement
between IIgs and 8-bit programs. Maybe there should be two
categories but if that's the case then the already small contestant
pool is split.

>>(5) 256 bytes maximum object code size.
>
>The original PC contest wanted code AND data to all fit in 256 bytes.
>Here is a question I have:  Does bank 0 locations count as data?  If 
>you are using JSR $FDED to display characters, then $24 and $25 will 
>get modified.  I think this should be ok, but you can't use bank 0
>for your own data (you may read and set known bank 0 locations,
>i.e. find cursor location, turn on/off inverse, etc...)

I can see limiting code + static data to 256 bytes but are you
saying that the program shouldn't be able to use any memory
outside it's alloted 256 bytes? I think that is a bad rule. For
example I think that a program ought to be able to generate
code at runtime that exceeds the 256 byte boundary. Also a program
ought to be able to use as much space as it wants for data as long
as it is generated at runtime and not part of the memory image.
In other words, I mean that I think the best rule is that the
static memory image that is loaded for execution must be less
than or equal to 256 bytes, including code and data, what the
program does at runtime is up to it.

>I think all monitors routine should be 100% compatible with all 
>Apple IIs (i.e. the //c has different code in the area where the
>//e has its casettte routines)

That's why I think there should be a standard machine
that the code must be able to run on. The programmers can then
assume that any facilities of that standard machine may be used
and any facilites which may be on other Apple II computers, but
not on that machine may not be used.

>One other thing... Should there be any assumptions of what mode
>the Apple is in when the program starts (i.e. 40 column mode,
>80 column mode, HGR already set, etc...)?

I don't think there should be any assumptions.

>Also: if your program is a system program (i.e. file type sys), then
>the bytes which are needed for the loader does NOT get counted for 
>your 256 bytes.

If IIgs programs are allowed, I can see this. For 8 bit machines,
just don't make it a system program.

>>When does the contest end?
>
>I think 3 weeks is short of a time.  Maybe two or three months would be
>better so word can get out (to get the maximum number of voters and
>maximum number of entries).

I think that drags it out way too long. I think people will lose
interest. Also the 3 week total of contest + judging is counted from
the official start, I think people can work on programs before that time
it's just that I think 2 weeks from the offical start is about the
minimum time you'd want to write a program. Also there's no reason
why there can't be another contest after the first one is over so
there's no point in dragging it out for months and months just to
make sure that everyone in the world can hear about it an enter.

>No previuosly published programs may be submitted--any such entries will
>be disqualified.

I agree. Previously written should be ok, but previously published should
be disqualified.

-Sheldon

-- 
 W. Sheldon Simms III
 sheldon@netcom.com
 Newt's Friend -- Phil Gramm for President (No, Newt's NOT going to run!)