On Thu, 2020-04-16 at 11:04 +0200, Guillermo wrote:
> Thanks Swen.
>
> I see last commit was 2 days ago so it is active. I would like to
> know
> who is responsible to speak to him. May be I can help with the MSX
> target, but I need gidance about the internals of the compiler (I
> tried
> but it
On Thu, 2020-04-16 at 11:04 +0200, Guillermo wrote:
> Thanks Swen.
>
> I see last commit was 2 days ago so it is active. I would like to
> know
> who is responsible to speak to him. May be I can help with the MSX
> target, but I need gidance about the internals of the compiler (I
> tried
> but it
On Mon, 2020-04-20 at 17:07 +0300, nick...@gmail.com wrote:
> On Thu, 2020-04-16 at 11:04 +0200, Guillermo wrote:
> > Thanks Swen.
> >
> > I see last commit was 2 days ago so it is active. I would like to
> > know
> > who is responsible to speak to him. May be I can help with the MSX
> > target,
On Mon, 2020-04-27 at 15:40 +0200, Michael Van Canneyt wrote:
>
> On Mon, 27 Apr 2020, nickysn--- via fpc-devel wrote:
>
> > Last night, I got the full system unit to compile, including
> > console
> > output, so now you can use standard write/writeln. Unfortunately
On Mon, 2020-04-27 at 17:52 +0200, Karoly Balogh (Charlie/SGR) wrote:
> Hi,
>
> On Mon, 27 Apr 2020, Sven Barth via fpc-devel wrote:
>
> >> Well, I'm surprised and impressed you got it to work at all...
> >> Quite an achievement.
> >
> > Considering that we already support AVR as well I was rathe
On Tue, 2020-06-23 at 13:59 -0300, popolon...@popolony2k.com.br wrote:
> FPC Team.
>
>
>
> Thanks a lot. Everything is working fine. I compiled my first FPC
> code (simple hello world) to MSX-DOS2 and is working fine.
>
> The only thing I realized, is something someone here wrote before,
> tha