Copperlist crash?

[TCH]

Originally Posted by redblade

Probably to calculate how much CHIPMEM it needs to allocate and if it fails to return the error. It could have saved the programmers bytes in the 256K rom.

So, it's just a pre-check and not actual allocation? The manual says otherwise, beside

CBump()

's manual page does not says anything about extending the structure, just incrementing the pointer.

Originally Posted by redblade

Also the later RKM examples for OS 2+ modify the UCopperList to open up on a custom screen, code is 90% identical tho.

Yes, they do, but the original 1.3 one also could use a custom screen, not with taglists of course.

Originally Posted by redblade

Glad the battery didn't destroy your 500+

Me too, especially because neither battery didn't. Both the original and the replacement barrel lasted for roughly one and a half decade, but now a CR-2032 socket resides inside; easy to change the battery and no need to fear the chemicals anymore.

BTW, how can i suppress the error messages for this approach?

extern struct Custom custom;

...

CMOVE(copperlist, custom.color[4], cc[i]);

4096colors.c:91:3: warning: passing argument 2 of 'CMove' discards 'volatile' qualifier from pointer target type [-Wdiscarded-qualifiers]
   CMOVE(copperlist, custom.color[4], cc[i]);
   ^~~~~
In file included from 4096colors.c:4:0:
/opt/amiga/m68k-amigaos/ndk13-include/clib/graphics_protos.h:114:6: note: expected 'APTR {aka void *}' but argument is of type 'volatile UWORD * {aka volatile short unsigned int *}'
 VOID CMove( struct UCopList *copList, APTR destination, LONG data );
      ^~~~~

Aside from not using the

discarded-qualifiers

flag or write the code like this

CMove(copperlist, (void *)0x0188, cc[i]);
CBump(copperlist);

Works both way, but the warnings are flooding the console...

[TCH]

The program is now available here:
http://oscomp.hu/?details/4096_Colors_v1.0.0_Amiga_1575

[BippyM]

I have moved this thread into c/c++. I appreciate it is hardware related, but it's more c/c++ related

[TCH]

Well, the language itself was secondary, but okay. (It was more like AmigaOS related as the solution itself was to use the AmigaOS API.)