Ive been mulling this over for a while. Im at a point where the number of objects in my demo engine is growing painful manage. Rather than write out object something = new classT for each and every new object, is it possible to write a file parser / script interface that will generate objects and delete them?

for example:
if level1
run (level1script)

run(script)
//get create the objects
build(entities)
initialize(entities)

build(entities)
//get pointers to objects
for all entities
"name from file" = new entity

initialize(entities)
//initialize entities from file
for all entities
setAttributes(entity)

setAttributes(entity)
//read and return the attributes to initialize with
entity(findInFile(entity))

What I cant figure out is how to write code so that it will make objects based on whats written in a file. Can i just copy strings from a file and use some clever sprintf useage to get it to be a name, or do i set a vector to hold all the created objects of a given type and have the script manage whats where?

Sorry if this is all very confusing, Im just confused about it myself, but i cant imagine that every simgle object must be hard coded into c++. If its standard to do so please tell me though

ryan

You would generally want to have as much external data as you can. It will make editing a lot easier (and open a window to user modding if you want).
The only problem is if you dont want people to mingle with your data.