7604f2477b | ||
---|---|---|
.. | ||
script | ||
.gitignore | ||
EqualsHelper.cs | ||
ErrorHelper.cs | ||
HashHelper.cs | ||
Make.config | ||
Makefile | ||
NameGenerator.cs | ||
README.md | ||
classhelper.cs | ||
comparablehelper.cs | ||
driver.cs | ||
error.cs | ||
extensions.cs | ||
generate-version.sh | ||
generator.cs | ||
methodhelper.cs | ||
objcgen.csproj | ||
objcgenerator-helpers.cs | ||
objcgenerator-postprocessor.cs | ||
objcgenerator-processor.cs | ||
objcgenerator-subscripts.cs | ||
objcgenerator.cs | ||
objcprocessor.cs | ||
operatoroverloads.cs | ||
packages.config | ||
processedtypes.cs | ||
processor.cs | ||
protocolhelper.cs | ||
sourcewriter.cs | ||
system-check.cs | ||
system-dependencies.sh | ||
thin-framework.sh |
README.md
ObjC generator
Build
Simply run make
in Embeddinator-4000/objcgen
.
Run
Don't use Embeddinator-4000.exe
.
Use mono ./bin/Debug/objcgen.exe --gen=Obj-C -o ./Output ManagedAssembly1.dll
.
Generated API of questionable usability
Whenever we generate a working API that is not optimal (in ObjC) we should update the docs/BestPracticesObjC.md
document to explain the situation and provide guidance to get the best ObjC API output.
Missing .NET features
Unimplemented, but planned, features should throw a NotImplementedException
with the feature name. The generator will report it as a missing feature that does not require a bug report (and test case).
Unsupported .NET features
Anything that cannot be supported should be added to the docs/Limitations.md
document.
The tool should issue warnings (which users can turn into errors) when it cannot generate ObjC to match any given .NET code. The warnings must be added to the docs/errors.md
document.