Note that there are some explanatory texts on larger screens.

plurals
  1. POFileUtils uptodate? issue in Ruby
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThat code is weird, why accept options if you're going to raise an error when people provide them? And I don't understand the problem, if the build framework is so fast, then why does it matter if it occasionally recompiles a file? Unless you're saying that it recompiles the same file many times during the same build. If that's the case, then consider moving to a better tool. [Rake](http://jasonseifer.com/2010/04/06/rake-tutorial?again), for example, was built for this purpose, and deals with this via dependencies, so it wouldn't have such an issue.
      singulars
    2. CO@JoshuaCheek That code is part of the FileUtils module in Ruby (i.e. it was not written by me!). I am using Rake but I suspect it would behave the same way even if I specified the file dependencies (I am guessing it uses uptodate? internally?). I don't want the build framework to recompile/re-link/run a unit test unnecessarily, because when you are TDD'ing it does matter!
      singulars
    3. COMan, there's some weird code in the stdlib O.o Anyway, the difference (If I understand correctly what you're doing) would be that Rake would check that file only one time e.g. it would compile it exactly once, this is because rake tasks are not like methods, but rather like dependencies. File a depends on c, File b depends on c. If you compile both a and b, then c will be compiled once for a, thus the dependency is satisfied for c.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload