Yes, you are right.  I have modified this so it matches (or is similar) to the code used elsewhere ([See code](https://github.com/ssimpo/dojo/blob/t11750/dojo.js#L186-L196)).  It was not immediately  possible to copy the code as config is not yet created but have copied the logic use both userConfig.cacheBust and defaultConfig.cacheBust.

The code is now a bit verbose but it is at least consistent and allows people to specify a cacheBust variable rather than always expecting boolean; which, I guess is important.

Have added a TODO in my own code as something to think about.  It seems wrong to duplicate this code within dojo.js.  Perhaps there could be one function that does this early on?  Think that would mean moving stuff around though, which break things in unpredictable ways.  So, maybe one for the future? Or, just ignore?