Skip to content

Some feedback for thesis and code#6

Open
steve-s wants to merge 1 commit into
jagotu:masterfrom
steve-s:steve-s-feedback1
Open

Some feedback for thesis and code#6
steve-s wants to merge 1 commit into
jagotu:masterfrom
steve-s:steve-s-feedback1

Conversation

@steve-s

@steve-s steve-s commented Jul 14, 2022

Copy link
Copy Markdown
Collaborator

No description provided.



Is there anywhere explained why you chose bytecode style interpreter over AST? You could say it was part of the problem statement: is it feasible to implement .NET interpreter in one person and will using the bytecode interpreter approach pionieered by Espresso work for .NET and deliver cleaner/leaner/faster (interpreter speed) implementation than AST style interpreter already implemented by [...] and [...].

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mozna ze i otazka, zda parser nativniho .NET assembly formatu muze neco prinest (rychlost, lower memory, ...) by mohla byt formulovana jako soucasti zadani.


Truffle's official mechanism of calling into native code is called the Native Function Interface (NFI). Unfortunately, at the time of designing BACIL, it was missing key features, for example support of custom ABIs (calling conventions).

Dalo by se tohle vyresit tak, ze si clovek udela trampolinu v C, ve ktere uz muze udelat libovolny marshalling, volani pres jinou konvenci, atd. Ta trampolina by mela vhodnout volaci konvenci a brala by data ve formatu, ktery se hodil BACILu, ale pak by je mohla zmasirovat na cokoliv na nativni strane.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mel byt otaznik na konci

Comment thread GENERIC-NOTES
- Small number of tests
- I am not a big fan of "unit test every little trivial helper", but some amount of
integration tests like a bunch of C# programs and a driver that executes them on
BACIL/dotnet and compares the output would be nice. EDIT: I see there's the .NET's own test suite, that's good. Still some more custom tests would be great.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kdyz o tom vic premyslim, ty codegen testy z dotnet netestuji treba veci jako nacitani assemblies s ruznymi zavislostmi, nacteni nejake malformed assembly, nacteni assembly dvakrat, atd. veci tykajici se runtime ne primo compileru. To by byly i celkem smysluplne testy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant