> Ryan S. Dancey
>
> So here's an interesting thing and a pretty skewed way of looking at the
> problem.  The OGL says that the OGC must be clearly identified.
> It doesn't say that the OGC must itself be human-readable.

Ah, now we are getting somewhere.  That is how I read it as well.

> As an experienced programmer, I could probably load that section of the
> executable into a debugger or analyzer and start to make some
> sense of it if I wanted to take the time to do so, but that's a
> non-trivial task at best.

Agreed.  In this situation I think that languages like Java, C# and Visual
Basic would fare much better than C/C++ due to their use of bytecode
interpreters and virtual machines.  Their file layouts are well understood
(well, Java is anyway) and lack the near-unlimited freedom that a C/C++
executable has.  It definitely has potential.  It would still be nice if the
source were available though.

-Brad

_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://www.opengamingfoundation.org/mailman/listinfo/ogf-l

Reply via email to