I don’t think that was premature optimization, just some code from an old fart that had already been programming in the era where processors had reasons to use it:
Since then, I learned that since Windows Vista and up has timeout command that just waits:
timeout /t 600 /nobreak
Two parameters are used:
/nobreak
does not stop waiting when you press a key
/t #
waits # seconds
(the example is 10 minutes, I use it to regularly run FlushFileCache.exe or FlushMem.exe to empty the Windows file chache and release memory – often more than a gigabyte – back to Windows)
There is also sleep.exe, but that requires the Windows Resource Kit or Windows Server 2000/2003.
if exist PostBuild.bat call PostBuild.bat $(Platform) $(Config) $(OutputDir)
And then the PostBuild.bat script calls a Python script so that I can write my scripts in a real language.
I actually impose the build actions in a shared option set that I reference from all of my projects. That way I enforce consistency and predictability.
I know others use tools like FinalBuilder but building is so important that I feel it’s worth my effort in rolling my own tooling.
– David Heffernan Feb 14 at 20:24
One of the easy things in *nix is to set the value of an environment with the output of a command.
Something like this is possible in Windows too, but you have to instruct Windows to keep an empty set of delimiters to capture the full first line.
There is also a small but important difference between Windows and *nix upon command failure: *nix will always return an empty value, but in Windows you must make sure to empty the value first.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Yes, SQL Parameter names will probably less than 1000 characters, but then the 1000literal should be a constant with a meaningful name, and the '@' literal should be too. Read the rest of this entry »
OwlyCI is like NuGet for Delphi. They add Delphi open source repositories, and provide them as installable packages, and shows build statistics.
Ohloh provides statistics (including build statistics!) for open source repositories (any language and environment) and shows various other statistics like check in counts, LoC, etc. Koders merged into Oholoh about a year ago.