EQEmu Devleopment Guide
 

Hi all,

Just wondering, what’s the coding standard for the EQEmu Project? I.e. How to name the methods, properties, how is the code laid out, etc.

If no, I would like to propose one which has input from all people community.

We need input from the current dev's for this so that we can align the standard with their dev style also.

I also higher recommend we use the C++ Standard for layout & Development, i.e. 1 class per file and alike.

Cheers,

- froglok

By the way, here is the C++ ISO Standard: http://www.iso.org/iso/iso_catalogue...csnumber=38110 (appears you have topay for it.. jibbed)

But then again, here the ECMA Standard, http://www.iso.org/iso/iso_catalogue...csnumber=38110

WHICH you can order for nothing at:
http://www.ecma-international.org/pu...ions/getit.php the Code is: ECMA-372 (ordering one myself, I have the C# and its WELL worth it) and its FREE!!!!

- froglok

I am not a C++ coder by any means, but isn't the emu architecture laid out in the wiki? It never made much sense to me, but looked impressive. Not sure if that's what you're looking for.

http://www.eqemulator.net/wiki/wikka...oryDevelopment

Under all the porn and viagra links, there's actual info. ;)

Code isn't completely one class to file. It's usually pretty easy to find something in the code.

For example mob.cpp contains functions related to the Mob class.. client.cpp functions related to Client class. Yet bonuses.cpp for example contains functions related to calculating bonuses which applies to Mob, Client and NPC classes.

Not sure if there's an official standard for function naming, from what I've seen and been instructed to do was try to make it as clear as possible.

Yeah, very true KLS, I doubt theres a standard on function naming, but as long as it is targeted to what teh funtion actually does, following it shouldnt be a problem.

-froglok