Compiler say ERROR, but where?

Message

FanDjango · #1 Post by **FanDjango** » 13 Dec 2008 21:15

PASCAL AVR PRO Beta, unregistered Demo Version, Source is large and should produce DEMO LIMIT.

Instead, I get the following output.

No indication of any error, but cannot program either.

stevech · #2 Post by **stevech** » 14 Dec 2008 00:56

In the linker? Does it have an output file?

FanDjango · #3 Post by **FanDjango** » 14 Dec 2008 11:48

No other sensible files other than

TEST1.LOG

Code: Select all

Line	MessageNo	File Name
0	1	mPAVR.exe -DBG -pATMEGA644P -MSF -O11111115 -fo8 -N"C:\Users\Michael Stiemke\Documents\mE\TEST1\test1.mppav" -SP"C:\Program Files\Mikroelektronika\mikroPascal PRO for AVR\Defs\" -SP"C:\Program Files\Mikroelektronika\mikroPascal PRO for AVR\Uses\LTE64KW\" -SP"C:\Users\Michael Stiemke\Documents\mE\TEST1\" "__Lib_Math.mcl" "__Lib_MathDouble.mcl" "__Lib_System.mcl" "__Lib_Delays.mcl" "__Lib_String.mcl" "__Lib_Conversions.mcl" "__Lib_SPI_b567_x2.mcl" "__Lib_Mmc.mcl" "test1.mpas"	 
diagnostics: 0	132	Compilation Started	C:\USERS\MICHAEL STIEMKE\DOCUMENTS\ME\TEST1\test1.mpas
hint: 157	1018	Warning: Suspicious pointer conversion	test1.mpas
hint: 364	1011	Hint: Variable "zsec" has been eliminated by optimizer	test1.mpas
hint: 369	1011	Hint: Variable "rclun" has been eliminated by optimizer	test1.mpas
hint: 370	1011	Hint: Variable "yclusec" has been eliminated by optimizer	test1.mpas
hint: 390	1011	Hint: Variable "j" has been eliminated by optimizer	test1.mpas
hint: 393	1011	Hint: Variable "zsec" has been eliminated by optimizer	test1.mpas
hint: 398	1011	Hint: Variable "rclun" has been eliminated by optimizer	test1.mpas
diagnostics: 0	133	Compiled Successfully	C:\USERS\MICHAEL STIEMKE\DOCUMENTS\ME\TEST1\test1.mpas
diagnostics: 0	137	All files Compiled in 750 ms	 
0	0		
error: 0	102	Finished (with errors): 14 Dez 2008, 11:42:38	test1.mppav

and the TEST1.LST, which looks strange:

Code: Select all

unit |;


implementation

end.

TEST1.ASM looks real good and is nice and long, contains all the translated source - i.e. it seems quite complete

yo2lio · #4 Post by **yo2lio** » 14 Dec 2008 12:53

Please zip the project folder and sent to florin@microelemente.ro

FanDjango · #5 Post by **FanDjango** » 14 Dec 2008 13:51

Done. Good Luck

yo2lio · #6 Post by **yo2lio** » 14 Dec 2008 14:25

Done !

I don't know why , the compiler don't accept instructions like this :

Code: Select all

usay(' '+#13+#10);

I made changes in the code with this :

Code: Select all

buf_txt := ' '+#13+#10;
usay(buf_txt);

Also , MMC library need this declarations :

Code: Select all

var MMC_chip_select : sbit at PORTB.B4;
var MMC_chip_select_direction : sbit at DDRB.B4;

Now compile OK !

FanDjango · #7 Post by **FanDjango** » 14 Dec 2008 14:31

Well Done! :D

But mikroElektronika: You should fix the behaviour of the compiler. The stuff the compiler doesn't accept should lead to an error message. Also, a missing declaration should be an error.

Thanks for fixing it for me - but the main point is for the BETA Version to be corrected of such misleading behaviour.

yo2lio · #8 Post by **yo2lio** » 14 Dec 2008 14:37

FanDjango wrote: Also, a missing declaration should be an error.

It is ... without declarations i got this error messages :

0 359 Unresolved extern 'MMC_chip_select' __lib_mmc.mpas
0 359 Unresolved extern 'MMC_chip_select_direction' __lib_mmc.mpas

FanDjango · #9 Post by **FanDjango** » 14 Dec 2008 14:40

I am right now experimenting exactly WHICH statements of the ones that you changed are causing the strange behaviour

FanDjango · #10 Post by **FanDjango** » 14 Dec 2008 15:11

Ok.

It is EITHER one of THESE two statemenst:

Code: Select all

usay(' '+#27+'[12l')
usay(' '+#27+'[20l')

All the others can stay the way they were.

So when one of the two statements above are used instead of your circumvention, you get the strange compiler behaviour.

So I created a mini program with such a construct, but in a small mini program, "usay(' '+#27+'[12l')" does not make the compiler go wrong.

It must also have something to do with the program being larger or whatever.

goran.marinkovic · #11 Post by **goran.marinkovic** » 16 Dec 2008 11:43

Hi,

Please post this question on our Support Desk:
http://www.mikroe.com/en/support/
And provide us with piece of code which demonstrate problem.
Also explain your problem as much you can.

Regards

FanDjango · #12 Post by **FanDjango** » 16 Dec 2008 12:06

Done! Good luck!

goran.marinkovic · #13 Post by **goran.marinkovic** » 16 Dec 2008 14:03

Hi,

At mikroElektronika we are always glad to receive suggestions
and feedback from our customers.
Thank you for your feedback, and please feel free to
inform us about any other problem or suggestion you might have.

Regards

goran.marinkovic · #14 Post by **goran.marinkovic** » 17 Dec 2008 14:26

Hi,

Mentioned issue will be corrected in coming release(very soon).

Thanks

luko · #15 Post by **luko** » 11 Mar 2009 12:57

program test;
var s:string[2];
a:byte;

begin
s:='x';
case s of
'x': a:=1;
end;
end.

result:
compilation startet
finished (with errors) but it found neither warnings nor errors.
The compiler must check the variable-type of the case statement

Compiler say ERROR, but where?

Compiler say ERROR, but where?

another reason for "finished with errors" without

Copyright© 2020 MikroElektronika d.o.o.