[Wine] Re: Legal Issues

[oiaohm]

My english sux yes that is nothing new to me.

magic code/magic values is a old term normally used in legal cases about breaches.   Not exactly a general term you will find any where.   People performing magic can make items seam to appear from no where by slide of hand.    Magic code and magic values are the same kind of thing.  If you understand where they came from they are no longer magic.

http://en.wikipedia.org/wiki/Magic_number_%28programming%29 Use of magic for strange things in programming is a really old term.

Basically magic code/magic values are unexplainable appearances of stuff.   Where unexplained appears is unique to the development method.

Program written completely new from scratch normally will contain no magic items everything will be appearing out of the natural cycle.

Program written new but using a standard file format and other documents can have some data from the documents appearing in the program like magic.  One of the most common magic values is the magic number used to identify file types. 

Program written by black box will have magic values appearing as stubs first then the stubs latter on developing threw to more and more functional functions.

Program written by clean room will have a lot more magic items appearing without a development cycle to get there.   Basically the stuff appearing like by magic is evidence.    Basically it the stuff appearing by magic that tells you what the developers are doing.

Remember black boxing does include running MS Dlls in contained environments monitoring data sent to them and there matching requests.  This is still test casing.  At no time is the black box of the dll disassembled.   Black boxing also uses the substitution test.  You think you have worked out the black box so you substitute it with you own implementation and see if it still works right.   That is what WineD3D debugging recommends.

Wine's Direct3D implementation  << Need to be read a whole.  That is not MS Direct 3D.  Wined3d is wine's Direct3D implementation.   Problem is for new people working on wine it sometimes required to place documentation where they would expect to find it army_ant7.

If you read the direct3d debugging page you will notice the tittle is Direct3d but then it starts talking about Wined3d.

In WineD3D on windows it lists wine replacement direct dlls that will work on windows and other issues using wine parts.  Virtual machine builders of wined3d send wined3d directly to the ICD.  They made the ICD so they know what is there.

Opengl is a open standard.  Wine mostly does not have a opengl implementation instead its mostly a direct pass through with emulated interfaces of wgl written directly from the standard documentation.  wgl interface opengl32.dll has is fully documented.   No reversing or black-boxing required.  Note Fully documented by MS of all things and correct.  This is very much shock horror is one of the few API that MS has documented that they have not had a function with a glitch somewhere.

PS with me its grammar or spelling army_ant7.  I can only do one or the other.