Best Practice re: functions

[OneManClan]

[frag.machine]

The problem with all-in-one code is when you want to debug it or when you want to reuse part of it somewhere else. If the function is small and simple enough (like the stun effect you posted) it's no big deal, but try to do the same to say, monster spawning or behavior and you'll see what I mean. QuakeC is hard enough to debug without adding non necessary complexity.

[Spike]

[OneManClan]

Thanks for the feedback guys.

It's not so much 'smaller code' /fewer functions I'm concerned about; its more that I don't know what the 'best practice' is when it comes to qc (I've changed the subject accordingly).

Someone on #qc mentioned a while ago that there was some version of quake (original NetQuake?) which was considered 'the standard' when it comes to 'how the pros do it'. But I'm using heaps of new language features of FTEQCC, so I'm not even sure if the 'old ways' are still the 'best ways'.

ps Spike, thanks for the fork info.. will investigate further..
pps Or should I?

[ceriux]

idk maybe its just opinionated? if it works and you can read it. what does it matter? i personally like to make my qc as small as possible when i can. but i also like to use seperate functions for seperate things, that way i can reuse else where.