Introduction

The purpose of BLOOP is to reduce the programming time, creating by some clicks some redundant code for user defined types.

For example, how many times did you need a function that returns the number of objects of a particular type?

the function count(type) don't exists...

well with bloop, just copy and paste (or load file) the type (and the fields of course), click on create and the code is automatically created!

Now Bloop supports creation for this routines..

• Parameter Constructor (create a type with parameters!)
  
• default destructor (destroy a single object)
  
• destroy all types (and recursively all subtypes)
  
• Copy constructor (create and copy all fields from another)
  
• Operator equal (compares two objects)
  
• count (how many of this type?)
  
• dump (show all infos about the type)
  
  

Next to be realized...

• Load & save type
  
• GetAt and setAt in the main collection
  
• ifExist test
  
• and many many other
  
  

How does it works?

Simply replacing some strings of pre-defined code.

A sort of C++ preprocessor (that's why the name :)

Is written in VB6 and is easy to create some extra commands.

Knowed bugs & troubles

1. Well, the actual main problem is to create instructions for arrays. Not so hard, but requires some days...
   It's depends on how much is your feedback
   
2. Some objects contains integer that are handlers for entities / textures/ fonts/banks etc..
   
   
3. These fields can be divided in entities aggregated (contained and controlled) or referenced (only pointed)
   to avoiding side effects with some destruction/creation instructions.
   For example if a field object\pivot is only an handle to an entity pointed by a lot of other objects,
   it must be avoided to destruct the pivot calling the default destructor.
   (if you don't understand, don't warry..it's me :)