Code center > Suggestions

Simoltaneous DNA execution

<< < (3/8) > >>

Numsgil:

--- Quote ---A softwear must always be backwords compatible unless the old virsion is complete jibrish, but in this case its not , in 2.35 math is easyer to do then in what you prapose here.

Making a new "button" makes it no more backwords compatible
--- End quote ---
So when you say something like this, it's a good idea to reference back to the person who said something like it already.

IE:

I agree with Numsgil, A softwear must always be backwords compatible unless the old virsion is complete jibrish, but in this case its not , in 2.35 math is easyer to do then in what you prapose here.

Making a new "button" makes it no more backwords compatible

Botsareus:
Num , think about it if we put a new button for liner Dna execution. That means we are seporating the old robots from the new robots. If we have some robots on the screen with liner execution and nonliner in the same time, then there is no fear balance in the simulation. Seporating old robots from new robots does not solve the backwords compatability issue!!@@!!!!!! , you see now?

Hey, I give you credit , at least you agree that "A softwear must always be backwords compatible"

Numsgil:

--- Quote ---Seporating old robots from new robots does not solve the backwords compatability issue!
--- End quote ---

Yes, it does.  Are we talking about the same definition of backward compatible?

backward compatible - able to use old files in the new version


--- Quote ---Hey, I give you credit , at least you agree that "A softwear must always be backwords compatible"
--- End quote ---

There are some instances where backward compatibility is destructive to the final product.  But I think that most of the time if you can do it, you should.

Botsareus:
backward compatible - able to use old files in the new version and/with new files. Therefore allowing for fear competition between the files.

Yea my definition is a (little bit) more complex.

P.S.

Before I Studied how they made a cadd program backwards compatible; It was fear competition between the old files and new files because the I.o. was the same for both types of files and the user.

Botsareus:

--- Quote ---There are some instances where backward compatibility is destructive to the final product.
--- End quote ---

I agree 100% , but they [you]some[/you] instances. Not all instances.

Navigation

[0] Message Index

[#] Next page

[*] Previous page