Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user maak ! (Registered 2024-04-18) You are not logged in - nap
CSDb User Forums


Forums > C64 Coding > Kick Assembler Thread 2
2009-07-21 17:20
Slammer

Registered: Feb 2004
Posts: 416
Kick Assembler Thread 2

The previous thread took a little long to load, so this is a new fresh one..
 
... 590 posts hidden. Click here to view all posts....
 
2013-05-13 08:40
Oswald

Registered: Apr 2002
Posts: 5017
agreed.

for me more of a selling point is the nice capability of importing gfx/textures, or calculating sines, but am simply yet too lazy to make the move.
2013-05-13 10:46
Cruzer

Registered: Dec 2001
Posts: 1048
Just make the move for new stuff. No need to convert all your unreleased stuff right away. I still have old crappy routines in MxAss and TurboAss format lying around.
2013-05-13 12:09
soci

Registered: Sep 2003
Posts: 473
Right, 1.46 is quite bit outdated now. Creating sine and other tables is easy on 1.5x if that helps.

Importing raw data is no problem with almost any assembler. If it needs serious processing beyond chopping it up into pieces (e.g. conversion, compression, etc.) it's better to use the most suitable language/tool to do that part of the job first.
2013-05-13 13:49
chatGPZ

Registered: Dec 2001
Posts: 11101
Quote:
Gropaz: Lol. You do realise that your behaviour have put all of your requests to the backend of the queue, right? If you really are forced to use Kick Assembler, putting yourself in a position with no influence on future features, really seams like an excellent strategy. ;-)

i realised its pointless to argue about these things many moons ago, and that omitting certain core features is apparently a design goal of this assembler. if you think i am still expecting you to fix them, no. you have made clear you dont care at all and dont even understand why you should do that. (another point for ca65 here, or rather for Uz)
2013-05-13 16:21
Oswald

Registered: Apr 2002
Posts: 5017
tastes are different there are enough types of assemblers out there for everyone, kickass is amongst the best, and I respect slammer for it. compilers are amongst the most complex things one may code.
2013-05-13 21:44
Slammer

Registered: Feb 2004
Posts: 416
Groepas: I actually agreed with you, that some of your request would be nice to have and put them on the todo list. But since they didn't get implemented at once you got very aggressive and insulting. Do you actually expect people to hurry up using their spare time to implement the features you want, after you insult them? I thinks that your behaviour against me and several other people here on csdb speaks for it self. You really owe a lot of people an apology.
2013-05-15 18:37
Burglar

Registered: Dec 2004
Posts: 1031
now, now, boys. no need to get all frisky ;)

I like kickass a lot, and it would be even better if the suggested changes got implemented (like incbin).
2013-05-17 18:07
Slammer

Registered: Feb 2004
Posts: 416
Burglar: Incbin is one of the things that is on the todolist. Meanwhile check this thread for how to define a macro in 4 lines that can do the exact same thing : Need a coder
2014-12-17 10:40
Lead

Registered: Dec 2004
Posts: 20
I couldnt find a better topic to post this in, but I've got a naming challenge for macros with Kick.

If I use one of the macro's of Codebase, or write one myself, I would like to use the filename of this macro to name the memory area properly in the Memory map output of Kick. But whatever I seem to do, I cannot attach the filename to be part of the name of the memory area.

There's probably a way to do it but I cant find it in documentation, this form or anywhere.

The macro might look something like (pseudocode):

.macro MacroName (filename, address) {

.pc = address "Tables"

}

I would like to add the filename as send to the macro the the memory name (MyName) so it would be something like "Tables "+filename but i keep getting errors.

What is the proper way to use one of the variables send to the macro as part of the memory area name ?
2014-12-18 18:26
ruk

Registered: Jan 2012
Posts: 43
@Lead: I've previously failed numerous attempts of doing the same thing. My conclusion is that the .pc directive can *only* take a string and not an expression as an argument for the name.

If you're reading this Slammer, +1 for supporting this :-)
Previous - 1 | ... | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | ... | 61 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Guests online: 69
Top Demos
1 Next Level  (9.8)
2 Mojo  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 Comaland 100%  (9.6)
6 No Bounds  (9.6)
7 Uncensored  (9.6)
8 Wonderland XIV  (9.6)
9 The Ghost  (9.6)
10 Bromance  (9.6)
Top onefile Demos
1 It's More Fun to Com..  (9.8)
2 Party Elk 2  (9.7)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.5)
5 Rainbow Connection  (9.5)
6 Wafer Demo  (9.5)
7 TRSAC, Gabber & Pebe..  (9.5)
8 Onscreen 5k  (9.5)
9 Dawnfall V1.1  (9.5)
10 Quadrants  (9.5)
Top Groups
1 Oxyron  (9.3)
2 Nostalgia  (9.3)
3 Booze Design  (9.3)
4 Censor Design  (9.3)
5 Crest  (9.3)
Top Swappers
1 Derbyshire Ram  (10)
2 Jerry  (9.8)
3 Violator  (9.8)
4 Acidchild  (9.7)
5 Starlight  (9.6)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.053 sec.