| |
xIII
Registered: Nov 2008
Posts: 210 |
Need a coder
I made two hires pictures for the 'C64 Double Screen Compo 2013'. I need someone to make it into a screenscroller (going left-right)and a sound needs to be added.
The WOW coders are inactive and allthough I got some help from Jox (thx mate) I don't think I can code this myself in time.
Don't expect too much from the pics (Made them in HermIRES but I'm not a good graphician :)).
So if you want to help me out, PM me. |
|
... 20 posts hidden. Click here to view all posts....
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
its just an example of how the decision to support one thing with a directive and not another is rather arbitrary and doesnt follow a design rule. ofcourse you want an .align directive for convinience. just like .incbin :) |
| |
Glasnost
Account closed
Registered: Aug 2011
Posts: 26 |
.byte is a useless syntax too as the following example show:
.fill $1,'G'
.fill $1,'r'
.fill $1,'o'
.fill $1,'e'
.fill $1,'p'
.fill $1,'a'
.fill $1,'z'
:D |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
Quote:.byte is a useless syntax too as the following example show:
correct. actually .fill is one of the very few directives that an assembler *must* support :) once you have .fill and a half working macro facility, you can even implement the mnemonics as macros easily (and again, you'd be surprised how many assembler work just like that internally) |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
Making an intermediate language of .fill and .macro is the way to go then ;-) |
| |
Count Zero
Registered: Jan 2003
Posts: 1932 |
grp: Name 15 please!
:)
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
and you'd be surprised how many assemblers work like that - it makes a lot of sense actually (implement a minimal subset in actual code, then implement all the rest in macros and tables - once done properly you have a nice target architecture and -cpu agnostic assembler).
the point however is, no matter how you actually do it (only pedantic idiots like me care about inner workings of an assembler, obviously =P) that you shouldnt leave that implementation to the user - because that only creates a lot of unnecessary confusion (as you can see in this thread even). that could even be solved as having a builtin set of macros, which then can be important using a specific directive (eg in ca65 .macpack cbm or .macpack longjump) |
| |
Stainless Steel
Registered: Mar 2003
Posts: 966 |
Hey, stay on topic plz!! Or i'll have to alert the mods! err ... wait :-D (/me ducks and runs) |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
Yes, better draw some ugly koalas to test with my routine, fuckers :-) |
| |
enthusi
Registered: May 2004
Posts: 677 |
I always use .dsb ((*+$100)/$100)*$100-*,0
and I find it rather intuitive. Groepaz' solution is a bit more elegant though ;-) |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
Hmm.. Gpz smoked too much crack again. :) |
| Previous - 1 | 2 | 3 - Next |
