Sign in to follow this  

How to implement Entity-Component-System with C?

This topic is 1711 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi.
 
Recently, I read some articles about "Entity-Component-System", one of these is  "What is an entity system framework for game development?" written by Richard Lord.
 
In his article, he mentions that component only contains data which is like C's struct. Entity is a set of components which also don't have any method. All operation are moved to system.
 
This is data-oriented programming rather OOP, so why we still use OOP language rather than the C language? I'm interested  in what it will be when implemented in C.
 
One of the implementation may be like this:

    ecs_component_create("position");
    ecs_component_add_value_int("position", "x");
    ecs_component_add_value_float("position", "y");

    ...

    int id = ecs_entity_create("spaceship");
    ecs_entity_add_component(id, "position");
    ecs_entity_set_value_int(id, "position", "x", 0);
    ecs_entity_set_value_int(id, "position", "y", 0);
    ecs_engine_add_entity(id);

    ...

    ecs_engine_add_system(engine, "RenderSystem", priority);

 
 
I'm not sure whether it is right, can someone give me advises?

 

My English is poor, and thanks for your patient!

Share this post


Link to post
Share on other sites

Are you suggested effectively storing entities and components in giant string tables?

 

I'd have thought that Systems would be better placed to be isolated functions in this case and you just call them all in the game loop.

Share this post


Link to post
Share on other sites

Are you suggested effectively storing entities and components in giant string tables?

 
Right, as different Component has different "value", e.g. Component "position" has two float value "x" and "y", we may be dynamic generate those values. Because there is no class in C, we couldn't extend from a base class like IComponet. So I store these dynamic generated values into a string hashtable, which key is "variable name", [/size] to describe a Component, just like we "describe" a class is in OOP language.
 
When we create Entity, we can pass the Component name we "described" before, the engine may allocated memory to store the Component's value which just like we create an object in OOP language. 
 

I'd have thought that Systems would be better placed to be isolated functions in this case and you just call them all in the game loop.

 

I agree with you. May be Systems have some function pointer like void (*on_update)(float dt), and we can assign different function for different System, right? But I'm not sure is it a good implemention, I'm still exploring.

 

Anyway, thanks for your replay and  any suggestion is aprreciated!

Share this post


Link to post
Share on other sites

This topic is 1711 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this