[SDL] Where SDL goes in your game

[Armond Sarkisian]

Hmm,

So it is better to keep everything minimal under the fewest number of
classes. I must admit, I do tend to want to "over" organize my programs but
I will think this over. Anyone else have any other suggestions?

On 11/8/06, Peter Mulholland <darkmatter at freeuk.com> wrote:
>
> Hello Armond,
>
> Wednesday, November 8, 2006, 5:43:55 PM, you wrote:
>
> > Hi everyone,
>
> > This is my first post in this forum and hoping to find some help. I
> started
> > SDL a few months ago and all is well except I have a problem with the
> entire
> > program's structure.
> >
> > When we create an SDL-based app, where do you put all the SDL data as
> far as
> > the entire program's structure is concerned. An example... suppose we
> have the
> > following classes:
> >
> > - GameObjects  ( super-class )
> >
> > - Ball ( derived-class )
> > - Paddle ( derived-class )
> <snip>
>
> My two cents. Please do not get Java-itis and write your games so that
> every little thing is an object. It's inefficient, it's difficult to
> follow, and if you have to port such code (as I do) it's a total pain
> in the ass.
>
> --
> Best regards,
> Peter                            mailto:darkmatter at freeuk.com
>
>
> _______________________________________________
> SDL mailing list
> SDL at libsdl.org
> http://www.libsdl.org/mailman/listinfo/sdl
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20061108/0366c776/attachment.html