Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2013-11

MSElang, the future compiler for MSEide+MSEgui

11 messages · 4 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Marco van de Voort
to Martin Schreiber

In our previous episode, Martin Schreiber said:

Show quoted text 5 lines
A Wiki about the future compiler has been started: https://sourceforge.net/p/mseide-msegui/wiki/MSElang/ Please join the mailing list https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk if you like to discuss the matter.

You might want to have a look at Modula-2 R10, another attempt to redesign a wirthian language:

https://bitbucket.org/trijezdci/m2r10/src

if only for the way of documenting the design.

Reply by email

Marco van de Voort
to Martin Schreiber

In our previous episode, Martin Schreiber said:

> You might want to have a look at Modula-2 R10, another attempt to redesign > a wirthian language: > I used A+L Modula-2 at Amiga times. Good memories. :-)

I already guessed because of the "only end;" :-)

Though the R10ers borrowed a bit too much from C++ for my taste, and don't aim for self-hosting from the start. I like their project setup and way of documentating more than their output :-)

Reply by email

Michael Schnell
to Martin Schreiber: A Wiki about the future compiler has been started:…
Martin Schreiber wrote
if you like to discuss the matter.

IMHO this theme is complex enough to start another mailing list instead of discussion it here.

There already has been a (IMHO very interesting) discussion in the "German Lazarus forum" that in fact does have an "mse" section for such issues.

For me, there were some some discussion results that seem to be seem worth noticing (OS some are just my opinions :-) )
- Martin wants to beat the compiler speed of D7, which he esteems to be 10 times that of fpc. Good luck :-) :-) !
- IMHO, the archs supported should include X32, X64, ARM32, and ARM64
- IMHO, the OSes supported should include Windows (Desktop) and Linux. (Android would be nice but how to do this ?)

- There has been a vivid discussion on Unicode support. For me, the results are:
. - There should be no string type (out of the box) called "String" or ANSIString or "UnicodeString" (the user can add a "Type" statement if he wants such.) String types should be given "honest names. . - (Rather) decent Unicode handling can only be done with "code aware Strings", which Martin does not want to implement. This of course makes mseLang not really "Unicode aware", which is not a severe problem to most potential users, and in many cases better than not doing Unicode at all.
. - For optimum practical use the language should have a (raw) "ByteString" type and a "UTF16String" type that hold exactly the named information.
. - The appropriate Character Types of course are "Byte" and "UTF16Char" . - ByteStrings are not printable and there is no auto-conversion . - printable information always is in UTF16Strings. . - The string index (including pos(), ...) is counted in (16 bit) codewords. There is a decent documentation that shows the implications regarding Codepoints > 2^15 and "composed" printable characters. .- String (and array) indexes always count from Zero (neither base 1 (Strings) nor Base whatever Arrays).

I vote for adding Syntax for parallel processing (similar to "parallel loop" and "future" in Prism) but this of course is a future nice to have add-on.

have fun,
-Michael

Reply by email

Martin Schreiber
to Michael Schnell
Michael Schnell wrote 6 lines
On 11/06/2013 09:14 AM, Martin Schreiber wrote: > if you like to discuss the matter. IMHO this theme is complex enough to start another mailing list instead of discussion it here.

[...]

Please do not discuss MSElang here, I will not answer unless Jonas requests it. Please use the mentionend mailing list.

Thanks, Martin

Reply by email

Michael Schnell
to Martin Schreiber
Martin Schreiber wrote
Please do not discuss MSElang here, I will not answer unless Jonas requests it. Please use the mentionend mailing list

The post by Jonas seems to be private, as I don't see it in the list.

What did he suggest ?

-Michael

Reply by email

Jonas Maebe
to Martin Schreiber: [...] Please do not discuss MSElang here, I will not answer unless Jonas requests it.…
Martin Schreiber wrote 8 lines
On Wednesday 06 November 2013 10:36:19 Michael Schnell wrote: > IMHO this theme is complex enough to start another mailing list instead > of discussion it here. > [...] Please do not discuss MSElang here, I will not answer unless Jonas requests it. Please use the mentionend mailing list.

Or use fpc-other. It's indeed not really a topic for fpc-pascal.

Thanks,

Jonas
FPC mailing lists admin

Reply by email

Martin Schreiber
to Jonas Maebe
Jonas Maebe wrote 12 lines
On 06 Nov 2013, at 10:46, Martin Schreiber wrote: > On Wednesday 06 November 2013 10:36:19 Michael Schnell wrote: >> IMHO this theme is complex enough to start another mailing list instead >> of discussion it here. > > [...] > > Please do not discuss MSElang here, I will not answer unless Jonas > requests it. Please use the mentionend mailing list. Or use fpc-other. It's indeed not really a topic for fpc-pascal.

I do not read fpc-other and will not answer there.

Martin

Reply by email

Jonas Maebe
to Michael Schnell: The post by Jonas seems to be private, as I don't see it in the list. What did he suggest…
Michael Schnell wrote
On 11/06/2013 10:46 AM, Martin Schreiber wrote: > Please do not discuss MSElang here, I will not answer unless Jonas requests it. Please use the mentionend mailing list The post by Jonas seems to be private, as I don't see it in the list.

I had not yet posted anything. Martin himself asked to reply on another mailing list in his first message. I don't mind the initial announcement at all, but I agree with Martin that further discussion does not belong here.

Jonas

Reply by email