Box2D Forums

Hello,

I find it quite hard to quickly browse the source code to see what kind of classes it has and to see what it consists out of.

Especially with an external text editor like textpad.

I think it would probably be much better to split everything up.

Pretty much downto: one class per file.

The drawback would be "uses clausule" hell where everything has to be included.

Perhaps this can be solved by creating special types in one main unit like so:

unit Physics2D;

uses
everything here;

type
TSomething = unit.TSomething;

Perhaps something like that might work.

otherwise something like:

type
TB2Something = unit.TSomething;

At least this way the main unit can be included and have everything.

What you think of splitting the code up into multiple files ?

I think the main reason for one big file is because of "uses" problem... what if that problem was solved with method above...

Editing multiple files should also be pretty easy. So I dismiss arguments like: "editing multiple files is bad"

Editing multiple files actually always faster and more precise scrolling because source codes tend to be smaller.

Bye,
Skybuck.