coding style adherence

- markup codingStyleGuide.org examples so they actually indent correctly

- use 'Info<<' as per codingStyleGuide instead of 'Info <<'
This commit is contained in:
Mark Olesen
2009-11-27 15:39:14 +01:00
parent 51bdcca506
commit fa93ce8cd7
235 changed files with 702 additions and 634 deletions

View File

@ -183,7 +183,7 @@ int main(int argc, char *argv[])
Info<< endl;
}
Info << "End\n" << endl;
Info<< "End\n" << endl;
return 0;
}

View File

@ -16,7 +16,7 @@ if (Pstream::master())
if (Times[0].value() < 0)
{
Tcorr = - Times[0].value();
Info << "Correcting time values. Adding " << Tcorr << endl;
Info<< "Correcting time values. Adding " << Tcorr << endl;
}
for (int n=startTime; n<endTime; n++)

View File

@ -982,7 +982,7 @@ int main(int argc, char *argv[])
rm(fvParticleFileName);
}
Info << "End\n" << endl;
Info<< "End\n" << endl;
return 0;
}

View File

@ -62,14 +62,14 @@ int main(int argc, char *argv[])
// get the available time-steps
instantList TimeList = runTime.times();
Info << TimeList << endl;
Info<< TimeList << endl;
label nTimes = TimeList.size();
for(label n=1; n < nTimes; n++)
{
if (TimeList[n].value() > startTime)
{
Info << "Time = " << TimeList[n].value() << nl;
Info<< "Time = " << TimeList[n].value() << nl;
// Set Time
runTime.setTime(TimeList[n], n);

View File

@ -1,6 +1,6 @@
IOobject ioPoints
(
"points",
"points",
runTime.timeName(),
mesh.name(),
mesh
@ -8,7 +8,7 @@ IOobject ioPoints
if (ioPoints.headerOk())
{
Info << "new points available" << endl;
Info<< "new points available" << endl;
// Reading new points
pointIOField newPoints
(
@ -22,6 +22,6 @@ if (ioPoints.headerOk())
IOobject::NO_WRITE
)
);
mesh.movePoints(newPoints);
}

View File

@ -233,7 +233,7 @@ int main(int argc, char *argv[])
}
}
Info << "End\n" << endl;
Info<< "End\n" << endl;
return 0;
}