Sign in to follow this  

why did people said one advantage of abstract intereface is update of software.

This topic is 4593 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

just send customer the new file (containing new class and implementation)like: new dll. if you send customer file ,why not just send new main program ? to customer ,all he must do is copy file to directory of program, so what is different between copying a dll and copying main .exe?

Share this post


Link to post
Share on other sites
Because commercial engines are often designed modularly, with each part being in a dll -- so to update a section, you update the DLL and just send that as the update. Because everything is abstract, it shouldn't alter the rest of the way the program runs. Therefore, why would you resend the *.exe when all you really need to send is a mcuh smaller *.dll?

(this also applies to *.so)

Share this post


Link to post
Share on other sites
The customer doesn't care.

By using abstract interfaces, making the updated dll or exe is far far easier for programers, and will have fewer bugs since they only have to update the "concrete" part of the interface, not the interface itself, or every single part of the program that uses the interface.

Share this post


Link to post
Share on other sites

This topic is 4593 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this