graemeg

4 ms·

1.
by graemeg 5mo ago
That's exactly what I'm doing. :-) The world doesn't need another clone of FPC or Delphi. Blaise is Pascal for 2026+ without legacy baggage.
2.
by graemeg 5mo ago
Do you know if there is ongoing work to support x86_64 on Windows?
3.
by graemeg 5mo ago
Every new compiler needs to be bootstrapped by something - unless you head straight into Assembly Language from day1 - but I'm not that crazy! Yes, Blaise reached self-hosting after just 7 days. Meaning it could compile itself, and was
4.
by graemeg 5mo ago
fpGUI Toolkit will be made to work with Blaise. [1] Homepage (terrible looking): https://fpgui.sourceforge.net/ [2] Github repo: https://github.com/graemeg/fpGUI/ The Discussion area has some
5.
by graemeg 5mo ago
And FPC also supports interfaces without GUIDs via the {$interfaces CORBA} directive, and it too, supports the Supports(...) construct just fine. Delphi is just very Windows-centric with a lot of things they do.
6.
by graemeg 5mo ago
It's magic! ;-) Not wanting to go into too much technical details: Blaise's interface system uses TypeInfo pointers as identity tokens. Meaning manually added GUIDs are not needed. The two Supports() forms. Delphi has two overload
7.
by graemeg 5mo ago
Thank you. fpGUI is 20 years old this year! :-D
8.
by graemeg 5mo ago
Yes it has been fantastic to work with QBE so far. It's way simpler than LLVM, giving you about 70% of the LLVM performance, for 10% of the effort. :) Only downside is Windows support.
9.
by graemeg 5mo ago
Every new project starts at Day 1. :-)