Sign in Join

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

Mailing lists / fpc-pascal / 2015-01

Error Message recording not yet supported

7 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

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

Joao Morais

Hello list.

I got the "Message recordind not yet supported" error with 2.7.1 and 3.0.1 versions. 2.6.4 is fine. The error points to a zero-length line, between two class declarations.

I couldn't create a small sample, I cannot understand what is happening. If I remove a global {$WARN 5024 OFF} the code compiles again. If I use this same "warn 5024 off" on another projects I cannot reproduce the problem. Mantis has nothing related with warn 5024 or I couldn't find it.

The following steps shows the error message -- only v3, v2.7 has an $ifdef workaround:

- Download https://github.com/jcmoraisjr/jcore/archive/master.zip
- Compile a test package; or
- path/to/fpc/3.0.1/compiler/ppc386 -Ficore -Fucore -Fuopf -Fupath/to/fpc/3.0.1/rtl/units/<TARGET> opf/jcoreopfconfig

Please let me know if I did something badly wrong. Thanks!

Joao Morais

Reply by email

Tomas Hajny
to Joao Morais

On Wed, January 14, 2015 10:49, Joao Morais wrote:

Hello,

Show quoted text 18 lines
I got the "Message recordind not yet supported" error with 2.7.1 and 3.0.1 versions. 2.6.4 is fine. The error points to a zero-length line, between two class declarations. I couldn't create a small sample, I cannot understand what is happening. If I remove a global {$WARN 5024 OFF} the code compiles again. If I use this same "warn 5024 off" on another projects I cannot reproduce the problem. Mantis has nothing related with warn 5024 or I couldn't find it. The following steps shows the error message -- only v3, v2.7 has an $ifdef workaround: - Download https://github.com/jcmoraisjr/jcore/archive/master.zip - Compile a test package; or - path/to/fpc/3.0.1/compiler/ppc386 -Ficore -Fucore -Fuopf -Fupath/to/fpc/3.0.1/rtl/units/<TARGET> opf/jcoreopfconfig Please let me know if I did something badly wrong. Thanks!

First of all - do you get the message if compiling using a command line compiler? I can't find such a message anywhere in the compiler...

Tomas

Reply by email

Jonas Maebe
to Tomas Hajny
Tomas Hajny wrote
First of all - do you get the message if compiling using a command line compiler? I can't find such a message anywhere in the compiler...

It's hardcoded in the source code (scanner.pas:3320). It's kind of strange though: that error was added in the same commit that supposedly implemented storing/loading changed message states for generics. Maybe Pierre (who committed it) remembers why this is.

Jonas

Reply by email

Tomas Hajny
to Jonas Maebe
Jonas Maebe wrote 10 lines
On 14 Jan 2015, at 15:12, Tomas Hajny wrote: > First of all - do you get the message if compiling using a command > line > compiler? I can't find such a message anywhere in the compiler... It's hardcoded in the source code (scanner.pas:3320). It's kind of strange though: that error was added in the same commit that supposedly implemented storing/loading changed message states for generics. Maybe Pierre (who committed it) remembers why this is.

Oops - I searched the text appearing in the subject ('Message recording') rather than the one mentioned in the message (with the typo 'recordind' as included in the compiler) which is why I couldn't find it. :-( Thanks for looking at it more carefully.

Tomas

Reply by email

Pierre Free Pascal
to Jonas Maebe: It's hardcoded in the source code (scanner.pas:3320). It's kind of strange though: that…
Show quoted text 18 lines
-----Message d'origine----- De : [mailto:fpc-pascal- De la part de Jonas Maebe Envoyé : mercredi 14 janvier 2015 15:20 À : FPC-Pascal users discussions Objet : Re: [fpc-pascal] Error Message recording not yet supported On 14 Jan 2015, at 15:12, Tomas Hajny wrote: > First of all - do you get the message if compiling using a command > line > compiler? I can't find such a message anywhere in the compiler... It's hardcoded in the source code (scanner.pas:3320). It's kind of strange though: that error was added in the same commit that supposedly implemented storing/loading changed message states for generics. Maybe Pierre (who committed it) remembers why this is.

Hi all,

from looking at the source code and the commit,
it does appear to be some error..
The corresponding code that stores the message list generates an internal error if the number of message is more than 255. So that the two lines

  if mesgnb>0 then
    Comment(V_Error,'Message recordind not yet supported');

are probably just some wrong leftover.

The only problem is that we probably have no test
for this.

You can try to comment out these two lines and report if this fixes your problem.

Pierre Muller

Reply by email

Joao Morais
to Pierre Free Pascal
Pierre Free Pascal wrote 17 lines
Hi all, from looking at the source code and the commit, it does appear to be some error.. The corresponding code that stores the message list generates an internal error if the number of message is more than 255. So that the two lines if mesgnb>0 then Comment(V_Error,'Message recordind not yet supported'); are probably just some wrong leftover. The only problem is that we probably have no test for this. You can try to comment out these two lines and report if this fixes your problem.

I can confirm that removing such lines from the scanner solves the problem. Compiler messages also behaves as expected -- without warn 5024.

Reply by email

Joao Morais
to Joao Morais
Joao Morais wrote 17 lines
On 14/01/15 12:40, Pierre Free Pascal wrote: > The corresponding code that stores the message list > generates an internal error if the number of message is more than 255. > So that the two lines > if mesgnb>0 then > Comment(V_Error,'Message recordind not yet supported'); > > are probably just some wrong leftover. > > The only problem is that we probably have no test > for this. > > You can try to comment out these two lines and report > if this fixes your problem. I can confirm that removing such lines from the scanner solves the problem. Compiler messages also behaves as expected -- without warn 5024.

Hello list, the issue above was fixed as rev 29472. Is it possible to merge it to 3.0?

Thanks.

Reply by email