Re: [MSEide-MSEgui-talk] MSElang news.

2018-12-29 Thread Roland Chastain 

Hello Fred!

 

Congratulations for your work.

 

Regards.

 

Roland

 

Envoyé: samedi 29 décembre 2018 à 20:35
De: fredvs 
À: mseide-msegui-talk@lists.sourceforge.net
Objet: Re: [MSEide-MSEgui-talk] MSElang news.

Hello.

Here the MSElang project with Linux 32 binaries.

It works also in a Linux 64 bit multi-arch 64/32.

To install llvm, just do:

$ sudo apt-get install llvm

The MSElang project include the compiler: mlc, the interpreter mli and the
gui tool-chain: mselang and other tools.

Here the source + binaries:
mselang.zip


Unzip the file and run /mselang/mselang (this is a graphic app).

Choose a file to compile.
The default MSElang extension name is .mla but of course you may use a .pas
file.

Then click on "load".

Tip: to define the search-units path, click on param button and add
-Fu/thepath/units for example.
Right-click on the edit-panel to add rows.

And finally click on "parse".

See picture:


If you disable "llvm" option, only the mlc compiler will produce a .mli file
(that will be used by llvm).

You may test that mli file with the mli interpreter.
See picture:


Fre;D

.




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] MSElang news.

2018-12-29 Thread fredvs 
Hello.

Here the MSElang project with Linux 32 binaries.

It works also in a Linux 64 bit multi-arch 64/32.

To install llvm, just do:

$ sudo apt-get install llvm

The MSElang project include the compiler: mlc, the interpreter mli and the
gui tool-chain: mselang and other tools.

Here the source + binaries:
mselang.zip
  

Unzip the file and run /mselang/mselang (this is a graphic app).

Choose a file to compile.
The default MSElang extension name is .mla but of course you may use a .pas
file.

Then click on "load".

Tip: to define the search-units path, click on param button and add
-Fu/thepath/units for example.
Right-click on the edit-panel to add rows.

And finally click on "parse".

See picture:
 

If you disable "llvm" option, only the mlc compiler will produce a .mli file
(that will be used by llvm).

You may test that mli file with the mli interpreter.
See picture:
 

Fre;D

.




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] MSElang news.

2018-12-29 Thread fredvs 
Re-hello.

Here the Pascal code of the program:

{$mode mselang}
program hellomlc;
begin
writeln('Hello MLC');
end.

Here the bit code file produced by MSElang:
hellomlc_bc.zip
  

It would be marvelous is somebody that know LLVM could try to compile the
hellomlc.bc file to see what is wrong.
Maybe it is only the syntax of opt that I use tha is wrong.

I did use this:

/usr/bin/opt -O2 /home/fred/mlctest/hellomlc.bc

Fre;D

 

Fre;D 






--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] MSElang news.

2018-12-29 Thread fredvs 
Hello.

I am busy to test MSElang compiler:
https://gitlab.com/mseide-msegui/mselang

All went ok, the MSElang compiler produce a Bitcode File (helloworld.bc).

But when trying to compile that helloworld.bc file with *opt* there is that
error message
after +- 900 lines of messages of the opt compiler.

> /usr/bin/opt: /home/fred/mlctest/hellomlc.bc: error: input module is
> broken!

Where is the problem, do  you have a idea what appends ?

Thanks.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

2018-12-29 Thread fredvs 
Hello Mohamed.

> How do you plane this work?

I will try to bring together people that has some experience with MSE.

Roland Chastain has already answered that he is volunteer. 

Julio Jiménez said that he will help like I have been doing till now.

Graeme will surely help us at beginning for some Git things, like define the
list of maintainers.

Maybe you could be part of the team too?

When the good will team is formed ---> discussion.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

2018-12-29 Thread mohamed hamza 
Hi Fred;s,

I am  very glad that someone has the courage to engage in such complex task. 
Many thanks.
How do you plane this work?

Best Regards.

Med.

De : fredvs 
Envoyé : vendredi 28 décembre 2018 21:20
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

> My name is Bruno, I'm Martin's brother-in-law, I want to inform you that we
> have found in Martin's documents the pass words for MSEide-MSEgui
> sourceforge. In case you have already appointed a new leader
> (administrator?
> supervisor? manager?) for Martin's project, I would sent him the relevant
> data.

Hello Bruno.

Sincere condolence to you and all Martin family and friends.
Nice that you have found MSE-gitLab data access.
So this problem is already solved.
Many thanks.

For all the people of good will, positive and courageous that want to
contribute to maintain MSE alive.
Yes, Martin wanted to stay the boss, did not share commit-right to gitlab
easy.

But he was opened to discussion and it was possible to convince him.
Yes, he did prefer to commit code from himself (and not accept pull-request)
but he was honest to add a "Thanks to Julio Jiménez for the fixes"  (huh,
yes I did see it ;) ).

Now about MSE.

MSE is **giant** and I understand that everybody (include me) would be
terrorized to be responsible to resume Martin work.

But maybe we can split the MSE universe.

I am volunteer to maintain MSEide (because of ideU).

I am volunteer to maintain MSElang (because I am a explorer).
MSElang is a **pearl**, Martin has already something working, with RTL and
friends.
I did try it, it works.
But of course I do not have the skill for guru-llvm-thinks and when a
MSElang guru will appear, I will give him the keys.

I am volunteer to maintain MSEgui (because nobody has the balls to take that
responsibility).
But of course if there is people that have those things, please take the
keys.

I am volunteer to maintain MSEsak (because I am already the maintainer).

Other volunteers are of course welcome.

Come on guys, let's be positive, grateful, courageous, respectful and
creative.

Let's make a more happy new year.

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk