Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
1–10 of 59 posts
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#2[dead]
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#3Looks cool and does aim to address some of the annoying warts in Pascal. Especially the memory model.
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#4It is a bit curious with the Mojo 1.0 beta coincidence, as Pascal was the other langauge with a highly readable and quite simple language combined with performant compiled code without GC.
What it lacked was a modern compiler and stack. There is FreePascal for sure, and Lazarus is impressive, but it for sure has its baggage.
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#5That’s so great! Thank you!
I wish something like this existed for Ada :)
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#6Looks interesting. As someone who's been using Pascal since Turbo Pascal 6, and use Delphi daily at work, I'm not sure I quite get the "COM-style interface GUID" objection. What exactly about it is complex, and how do you implement Supports() without it?
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#7For me the only reason to use pascal is GUI apps but this doesn't have it.
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#8Looks interesting. As someone who's been using Pascal since Turbo Pascal 6, and use Delphi daily at work, I'm not sure I quite get the "COM-style interface GUID" objection. What exactly about it is complex, and how do you implement Supports() without it?
Not the OP, but I can answer with an objection to COM-style GUIDs myself. Delphi's interfaces are heavily based around COM, and so you need GUIDs, ARC, etc.
But interfaces as a concept don't require the COM backend. If you want your code to be cleanly separated, but don't want to split ownership/management models* (create/free vs ARC), and have no need for an interface and type identity to be managed outside your code and process (ie no COM), then interfaces that are not tied to ARC, and not tied to COM, give the clean code benefit without the baggage.
[*] People work around this by implementing interfaces from a base class with no-op AddRef/Release methods. But this kinda shows the problem: why is that necessary?
I work with Oxygene which is another modern Pascal -- quite a few new Pascals have popped up recently, I get the sense there's a real desire for something new! Our interfaces can be 'clean' and we support soft interfaces, too.
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#9It is a bit curious with the Mojo 1.0 beta coincidence, as Pascal was the other langauge with a highly readable and quite simple language combined with performant compiled code without GC. What it lacked was a modern compiler and stack. There is FreePascal for sure, and Lazarus is impressive, but it for sure has its baggage.
Yeah, Python and Pascal have always felt like they share similar vibes, despite being massively different languages. (Ease of writing, ease of reading, good inbuilts, etc.) Mojo feels like a clean take on similar goals... it's essentially a cleaner Python.
Re: Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
#10Looks interesting. As someone who's been using Pascal since Turbo Pascal 6, and use Delphi daily at work, I'm not sure I quite get the "COM-style interface GUID" objection. What exactly about it is complex, and how do you implement Supports() without it?
Not the OP, but I can answer with an objection to COM-style GUIDs myself. Delphi's interfaces are heavily based around COM, and so you need GUIDs, ARC, etc. But interfaces as a concept don't require the COM backend. If you want your code to be cleanly separated, but don't want to split ownership/management models* (create/free vs ARC), and have no need for an interface and type identity to be managed outside your cod…
But you don't need to specify a GUID for an interface in Delphi, and Blaise uses ARC for both objects and interfaces.