Re: [cadcdev-tiki] TikiBlap Demo 0.1

[Dan P. <ba...@al...>]

On Nov 29, atani wrote:

> Cool :)  In m y day job I mostly work in Java now so my C++ gets a  
> bit of influence from that nowadays..

Yeah, we're doing a lot of C# these days. I did Java earlier, the two are
kind of surprisingly similar (or not very suprising when you consider why
MS built C# :)

> Perhaps having an enum on Texture which we can add these as "flags"?   
> That way we can have a unified "base" which returns something like  
> "not implemented" for things like VQ/twiddle and then on the DC port  
> we can override this with a proper implementation.

Right. Or maybe down in Image since it has flags already and source
images would probably get loaded that way most of the time. Texture
could make use of the flags in Image also.

> Another thing to consider could be usage of exceptions within Tiki?

We've also been doing more of this at work. It's funny, these guys started
working with C++ when it was first coming out, basically just a
preprocessor around C. The attitudes from that time more or less got stuck,
so we have a lot of weird and gross stuff in the code base from the dawn of
time. Then we hired a bunch of new people who've studied modern C++
standards, design patterns, etc. Their influence is starting to cause us to
use things like exceptions finally. Well, that and MS building a *working*
C++ compiler :)

I'm somewhere in between. I like the plain bare-bones C++, especially in
an embedded situation, but I'm starting to like exceptions and RTTI a lot
more after using them in Java and C#.

Exceptions would sure beat some of the dumb 'assert' statements I have
scattered around in some inappropriate places ;)