Andrew Kunz wrote: > > I went and checked your site again: > > >Code must be fully commented (1 comment for every two lines in assembly, 1 > comment of every line in a higher level language). > > I don't know about the rest of the list, but I think these are WAY out of line. > This sounds like somebody who knows nothing about coding making policies for > programmers (ie, the pointy haired boss). Well, I would say use your judgment (as I believe many of us have good judgment), but I've run across so many badly commented pieces of code that I thought this was reasonable. Do you have a suggestion as to how I can word that so we don't end up at either of the two extremes? (too much commenting, too little commenting) > >If you choose a language other than assembly then one of the following must be > true: > > 1) The compiler is free, or your code example must completely compile under > the free version of the compiler you choose. > > 2) You also completely comment the assembly listing (1 comment for every > two lines) > > Well, Clyde just made the compiler of my choice available free in a limited > subset today. Problem is, it doesn't support your mandated chip. Now what? > > Since C is so portable () how about just making it in "C" is good enough. > > I htink you might get more takers if you made it so any commonly available > compiler (ByteCraft, HiTech, CCS) or assembler (HiTech, Tech-Tools, MPASM) can > be used. I don't care what you use or how much it may have cost. I just want to be able to assemble it in MPLAB for free. I just want to require that the code be submitted in assembly, and that someone who may not understand C or whatever language you use can still use your code (in assembly) in their program, or they can obtain, for free, a version of the compiler you use which will compile your code. I don't feel this is an onerous burden. I'll remove the requirement that the assembly code must be commented separately as long as you can generate an assembly file which includes your higher level code as comments (I have not yet seen a compiler which won't do this): ; TRISA = 0b.1100.0000; /* 7:6 Input(1), 5:0 Output(0) */ MOVLW .192 BSF 0x03,RP0 MOVWF TRISA ; TRISB = 0b.1111.1111; /* 7:0 Input, no output */ MOVLW .255 MOVWF TRISB ; TRISC = 0b.1100.0000; /* 7:0 Output */ MOVLW .192 MOVWF TRISC I'll also remove the requirement for a specific chip to be used. You can use any chip in the picmicro line. While I would like to keep the requirement that no external chips be used, that pretty much goes out the window if you plan on using an f'84 (excepting the serial sandisk). At this point it would be nicer to have the code than the restrictions. Please send your comments, I'll update the webpage today or monday with the sandisk contest, and any changes to the HD contest. -Adam