To Bundle or Not to Bundle - Printable Version +- The New C64 Forum (https://c64forum.com) +-- Forum: C64 and C128 (https://c64forum.com/forumdisplay.php?fid=4) +--- Forum: C64 and C128 Programming (https://c64forum.com/forumdisplay.php?fid=10) +--- Thread: To Bundle or Not to Bundle (/showthread.php?tid=363)

To Bundle or Not to Bundle - LivingLaVidaRetro - 07-14-2024 I feel this should be a decision I can make without having to get input, but to heck with it.  I figured I'd get some thoughts on the subject if for no other reason than to read some perspectives I may not have thought of. Consider a collection of mostly simple code routines - BASIC, ASM, doesn't matter.  Example routines may be: Prompt the user and read an integer Wait for a menu option, i.e. 1-9 Clear the screen with a cool effect. Convert a value from 1 form to another. The kinds of routines not program-specific, but written to be reusable anywhere. The Question: Do you release the routines as individual projects/repositories (.i.e. intprompter, menuselector, coolclear, valconverter), or all in a single project/repository (i.e. LLVRincludes)? I'm pretty big on creating these reusable type routines when I can.  I realize it can use more bytes and stack space but I prioritize modularity in my code until I need to save bytes/stack space. Thoughts?