Original Post
Ok, just a question about game engines. Ok well i have written my own simple game engine, the actual engine was something like engine.dll(had graphics functions and input etc.), then i had my game code stuff which was game.dll(used the engine.dll to render and load models and all the usual), then i had a loader program that loaded the game stuff in game.dll and whatever, sorry if thats a little hard to understand. Ok now i decided to read up on game engines, and as i was reading it said that the executable is the actual engine. like game.exe or whatever. Now im just wondering, if doing it all this way, using the game.exe with all your engine specific stuff in it and then maybe something like game.dll or whatever for information specific to your game would be a better way then what i was doing before, would it have speed worth while speed improvments doing it with the exe as the engine and then 1 dll for game stuff.. or would having 1 dll for my game stuff 1 dll for my engine and 1 exe for my loader thingy seem like it might work aswell.. i know alot of people may be saying, it doesnt really matter, just do which ever one you feel most comfortable and productive with. The thing is i know later on when the engine gets much bigger managing files and code and having it well structured will be a very important issue. Well thanks and any feedback will be greatly appreciated.