> The plans being discussed here will allow for very > precise compile-time checking of whether a clause > / expression is supported by a set of dialects > (except when choosing API union). There is no way > to "try things" that will not work, unless I'm > misunderstanding something?
Ad-hoc generation of the relevant subset of the API? Sure sounds cool, but also sounds scary. Also sounds like it's going to complicate the build process. Building is already a complicated thing in Java land; whatever the build activity, it needs to be easy to integrate into Ant, Maven, Gradle, SBT, and (hopefully) all the other cool build tools that will come along in the future. Oh, and it needs to integrate seamlessly with IDEs, and in my experience, that's the hardest subtask for getting the build under control - configuring Eclipse for an externally-run build step is clunky and not the kind of expertise that the average Eclipse user has. (I might be missing the point since I obviously missed that part of the discussion.) -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
