Yes, in my current implementation, the second function would not work, but to fit your build-system it must work.

As I see it, it's an issue over what is actually "correct" - and whose definition of correct we are talking about. Currently there is three different scenarios:

Standard RequireJS
```
define(['depA', 'depB'], function(depA, depB) {
  ...
})
```

RequireJS CommonJS comparability-mode 
```
define(function(require) {
  var depA = require("depA")
    , depB = require("depB")
  ...
}
```

Ace's build-format
```
define(['depA', 'depB'], function(require) {
  var depA = require("depA")
    , depB = require("depB")
  ...
}
```

The last, Ace's build format, seems to be identical to what's listed under the syntactic sugar for CommonJS compatibility: http://requirejs.org/docs/whyamd.html#sugar. But as far as I can tell, the listed conversion is a invalid RequireJS `define`-call, because if you look at how it's implemented (https://github.com/jrburke/requirejs/blob/master/require.js#L1991-2013) you can see that it only triggers CommonJS compatibility when there are no dependencies - i.e. it would not be triggered in the 3rd example (Ace's build-format). 
So I don't actually believe you could take the Ace build-format and actually load it with RequireJS. I have not tested this though, so I might be mistaken.

So the question is: Is it possible to support _both_ regular RequireJS syntax (example 1) and the Ace build-format (example 3), because this requires you to be able to tell the difference between the two, where the only difference is that the latter tends to have the first argument be called `require`, but this isn't actually a requirement, as you could call it anything.

---

I may be completely mis-guided here, as I cannot claim to understand all of RequireJS's code. I simply found their definition of `define` and how they handle CommonJS compatibility in there. There might be other parts somewhere else, that actually does ensures support for the Ace build-format, which I have just missed. 

So feel free to correct me if I'm wrong.