You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Giving one class at a time is ok while incrementally building up a suite but for a batch-like processes it is a lot of extra work and we could reuse the declaration that we already did in the types.properties file.
The text was updated successfully, but these errors were encountered:
It is now possible to generate for an entire package and all its sub packages. An improvement upon this I have planned is to be able to pass a list of classes.
jwausle
pushed a commit
to jwausle/frege-native-gen
that referenced
this issue
Dec 30, 2015
Enhance ‚frege-native-gen‘ cmdline:
$ frege-native-gen -c class1 -c class2 # to generate >1 class
$ frege-native-gen -t generate.all # to generate all classen
from types.properties
$ frege-native-gen # same as above
with default: types.properties
There is now a -c <comma-separated list of class names> option which allows us to be able to generate for a specific set of classes. We can now specify a package name or a set of classes to generate native declarations. More information on this here: https://github.com/Frege/frege-native-gen#how-to-run .
Giving one class at a time is ok while incrementally building up a suite but for a batch-like processes it is a lot of extra work and we could reuse the declaration that we already did in the types.properties file.
The text was updated successfully, but these errors were encountered: