Answer:
Explanation:
#include <iostream>
using namespace std;
int costdays(int);
int costhrs(int,int);
int main()
{
int dd,hh,mm,tmph,tmpd,tmpm=0;
int pcost,mcost=0;
cout<<"Enter Parking time" << endl;
cout<<"Hours: ";
cin>>hh;
cout<<"Minutes: ";
cin>>mm;
if (mm>60)
{
tmph=mm/60;
hh+=tmph;
mm-=(tmph*60);
}
if (hh>24)
{
tmpd=hh/24;
dd+=tmpd;
hh-=(tmpd*24);
}
if ((hh>4)&&(mm>0))
{
pcost+=costdays(1);
}
else
{
mcost=costhrs(hh,mm);
}
cout<<"Total time: ";
if (dd>0)
{
cout<<dd<<"days ";
pcost+=costdays(dd);
}
pcost+=mcost;
cout<<hh<<"h "<<mm<<"mins"<<endl;
cout<<"Total Cost :"<<pcost<<"Won";
return 0;
}
int costdays(int dd)
{
return(dd*25000);
}
int costhrs(int hh,int mm)
{
int tmpm, tmp=0;
tmp=(hh*6)*1000;
tmp+=(mm/10)*1000;
tmpm=mm-((mm/10)*10);
if (tmpm>0)
{
tmp+=1000;
}
return(tmp);
}
restart.is done after the computer is passed through configuration
Answer:
The key difference between a library and a framework is “Inversion of Control”. When you call a method from a library, you are in control. But with a framework, the control is inverted:the framework calls you
Explanation:
A library performs specific, well-defined operations.
A framework is a skeleton where the application defines the "meat" of the operation by filling out the skeleton. The skeleton still has code to link up the parts but the most important work is done by the application.
Examples of libraries: Network protocols, compression, image manipulation, string utilities, regular expression evaluation, math. Operations are self-contained.
Examples of frameworks: Web application system, Plug-in manager, GUI system. The framework defines the concept but the application defines the fundamental functionality that end-users care about.
the answer is the seconf one
