What about compiling for .NET? It is planned feature?

What about compiling for .NET? It is planned feature?

There used to be sb interested in it, but more for embedded use, however he has not spoken about it in a while, so I guess that died.

There hasn't been much interest of people to work on it since.

Since there is no real non win32 .NET OS in the picture, there is no real hurry anyway.

What would be the advantages of FPC compiling for .NET in your opinion?

Since there is no real non win32 .NET OS in the picture, there is no real hurry anyway. What would be the advantages of FPC compiling for .NET in your opinion?

.NET is not only for Win32! (AFAIK .NET for Linuxes is in development too.)

For example, I have the PDA. On this PDA is OS WinCE.NET. When I have program for .NET, then I can run this program on my WinXP and on my PDA too. (without any recompilation!) yes, I tried this and it really working!

And what about new 64-bit processors?

FPC can compile programs for Win32 with i386 processors. But what about new IA64 processors? I cannot use FPC for this! :-(

Now look to FPC features:
Support of FPC for WinCE platform? Not! What about ARM/XSCALE processors? NOT! What about new 64-bit processors from intel or AMD? NOT!

FPC is not usable for this platforms and processors. When FPC can compile to .NET, then you can create programs for all this platforms. it is IMHO very big advantage!

And what about next advantages of .NET? What about lot of existing code in .NET framework?

What about combining sources from another languages? You can create program, where part is written in C#, part is written in VB.NET... and part is written in pascal? it is not advantage?

ARM and x86-64 are under construction. iA64 will follow as soon as it's important.

The last time when I investigated .NET I found out that the creation of a .NET FPC release would be rather complicated because of MS licenses. The only solution would be to use mono but mono isn't ready to use yet.

My personal opionion is: I won't support creating another MS monopol by implementing .NET. More than 100 Sorbig mails per day and at least every minute an attack by lovescan are simply too much :)

But if someone is interessted, creating a .NET backend for FPC shouldn't be that hard.

Please calm down. There is no reason to scream. We already devote almost all our free time to FPC. So please don't ask for unreasonable things.

Here is a summary of the platforms:
- PowerPC is working
- ARM is in development
- SPARC is in development
- x86_64 development will start ASAP the developpers have hardware
- ia64, if you pay for the hardware... (using an external compilefarm is not an option)
- .NET, none of the current core developpers has plans to support it. You are welcome to implement it

Peter

ARM and x86-64 are under construction. iA64 will follow as soon as it's important.

ARM support is only one half of work. What about WinCE support?

Luckily enough my PDA runs linux ;)

> ARM and x86-64 are under construction. iA64 will follow as soon as it's > important. ARM support is only one half of work. What about WinCE support?

I don't have one, and the ARM developpers use Linux Zaurusses afaik.

So I don't see it on the horizon, since the FPC donations fund is also empty atm.

Hi,

What about 68k support in the 1.1 branch? I see there are some files in for it, but currently i see no sign if someone is working on in, or it will be in usable state in the near future. So what is the current state of 68k support? Dropped, suspended or developed with very low priority?

Bye,

The development has been suspended until someone starts development. Carl will stay with the 68k in the 1.0.x branch and not move to the 1.1 branch. Pierre has very little time, so there is also not to expect from him. The result is that nobody is working on it.

Those files are very old and i guess not much can be reused from those few files. It will be easier to start from scratch.

The development has been suspended until someone starts development. Carl will stay with the 68k in the 1.0.x branch and not move to the 1.1 branch. Pierre has very little time, so there is also not to expect from him. The result is that nobody is working on it.

Those files are very old and i guess not much can be reused from those few files. It will be easier to start from scratch.

Hi,

Interesting thread indeed.

Just pure curiosity.
I have recently bought a Nokia mobile with SymbianOS 6.x, but know nothing about the processor (I don't know much about ARM, I wonder if it runs under an ARM-compliable processor), is there any chance to have FPC to compile for my mobile (even after the ARM has been finished?). Sorry, I am still trying to get more technical information about it, but the manual is full of instructions of how to operate it, and hasn't got many technical valuable information, as usual ;-)

Aitor

Hi,

1.0.x branch? AFAIR, it was told that all developments stopped on the old compiler.

Pierre has very little time, so there is also not to expect from him. The result is that nobody is working on it. Those files are very old and i guess not much can be reused from those few files. It will be easier to start from scratch.

It seems to me, currently a lot of things morphing inside the compiler, around the code generator, register allocator, and things like that. When will these things stabilize? So is it worth make a try to begin a new code generator right now :), or it's more wise to wait for a while, until the new code becomes more stable on the rest of the platforms.

Bye,

It should have stabilized already.

Development is stopped. Carl wants to use the 68k version as it is now.

The CG part is stable. The RA is now in the development branch and is being stabilized. The 68k port can be started, in the beginning the dependency on the RA is not that much. First the cpubase and cgcpu need to be implemented.

You can ask Florian for help what the easiest way to go is. He recently started the ARM port with the CG already being stable.