I was having this same problem last night. I worked on it for a while to try to determine where the problem was, but never did figure it out. I will work on it some more tonight.

Any idea where that .s assembly file came from? I have never seen this file before now on anything else. I am going to look through the FPC documentation and see if it says anything about it creating this file. Also, I will try compiling with the -al switch like you did. It looks like that tells more than what I was getting. It is a difficult problem to solve because that .s file is created by the compiler. So I don't know if it is a bug in the compiler or a bug in the mwcustomedit code. Very strange.

Anyway, I will work on it some tonight and see what I can figure out.

Curtis

Has anyone from FPC looked at the assmebling issue that I submitted a few days ago? It still gives the error....

Here's the info I sent previously...

>

BUT, (there's always a but...) it doesn't assemble.

I do...

ppc386 mwcustomedit.pas
..
..
...
Assembling mwcustomedit
mwcustomedit.s: Assembler messages;
mwcustomedit.s:1273: Error: expecting operand before ","; got nothing Warning: error while assembling exitcode 1
Fatal: There were 1 errors compiling module, stopping

I did a ppc386 -al and

Line 1506 has the error. I'll give you the code here starting with line 1505...

# [1091] Result := inherited Font;
movl ,&eax
movl 420(%eax),%edi
..
...

As you can see, it expects something before the comma. Can someone look at this please....want me to send the .s file to someone?

>

Shane

I figured out what is causing this problem, but I don't know why. I am wondering if this might be a bug in FPC. Can one of the FPC guys tell me why this doesn't work in FPC (is it a bug or a feature)?

  Result := inherited Font;

When I comment out this line in mwcustomedit.pas, it compiles just fine. If this is not a bug in FPC, then we will need to figure out some other way to do this same thing. Anyone have any ideas?

So now we have it compiling, we just need to start implementing all the TODO's. Everyone, please feel free to help out with this. This is going take a fair amount of work to do.

Curtis