WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

User projects written in or related to FreeBASIC.
PaulSquires
Posts: 743
Joined: Jul 14, 2005 23:41
Contact:

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby PaulSquires » Feb 21, 2019 23:19

Whew! Nice to hear that is is not a WinFBE issue. :-)
PaulSquires
Posts: 743
Joined: Jul 14, 2005 23:41
Contact:

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby PaulSquires » Feb 21, 2019 23:20

fxm wrote:
fxm wrote:It would be nice if all IDEs also output the preprocessor texts (for example #print ...) inside the compiler result window (as for the compiler errors/warnings).
For example, it's true for FBIde but not for WinFBE.


This has now been implemented.

- Added: #print compile time messages are now output to the Compiler Results listview.

This will be in the v1.9.1 update.
fxm
Posts: 8748
Joined: Apr 22, 2009 12:46
Location: Paris (suburbs), FRANCE

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby fxm » Feb 22, 2019 6:11

Thank you.

Must work not only for #print, but also for #error:

Code: Select all

Dim As Object Ptr po = 1

Const MIN = 16, MAX = 10

#print typeof(MIN)

#assert MAX > MIN

Const 0MEAN = 13

#define c 1
#if c = 1
  #error Bad value of c
#endif
Compiler Log File wrote:FreeBASIC Compiler - Version 1.06.0 (11-22-2018), built for win32 (32bit)
Copyright (C) 2004-2016 The FreeBASIC development team.
standalone
target: win32, 486, 32bit
compiling: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMPBC9A.bas -o C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMPBC9A.asm (main module)
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMPBC9A.bas(1) warning 4(1): Suspicious pointer assignment
INTEGER
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMPBC9A.bas(5) error 308: #ASSERT condition failed in '#assert MAX > MIN'
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMPBC9A.bas(7) error 14: Expected identifier in 'Const 0MEAN = 13'
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMPBC9A.bas(11) error: Bad value of c
    XXXXX: OK
    XXXXX: To be also outputted in "Compiler Result" window.
fxm
Posts: 8748
Joined: Apr 22, 2009 12:46
Location: Paris (suburbs), FRANCE

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby fxm » Feb 23, 2019 14:11

The gcc compiler warnings are also not outputted in the "Compiler Result" window:
Successful Compile (Errors 0 Warnings 0)

Primary Source: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.bas
Target Compilation: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.exe (30 Ko
Command Line:
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\fbc32.exe -m "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.bas" "" -v -s console -i ".\FreeBASIC-1.06.0\inc\Afx" -gen gcc

FreeBASIC Compiler - Version 1.06.0 (11-22-2018), built for win32 (32bit)
Copyright (C) 2004-2016 The FreeBASIC development team.
standalone
target: win32, 486, 32bit
compiling: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.bas -o C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c (main module)
compiling C: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\bin\win32\gcc.exe -m32 -march=i486 -S -nostdlib -nostdinc -Wall -Wno-unused-label -Wno-unused-function -Wno-unused-variable -Wno-unused-but-set-variable -Wno-main -Werror-implicit-function-declaration -O0 -fno-strict-aliasing -frounding-math -fno-math-errno -fwrapv -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -masm=intel "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c" -o "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.asm"
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c: In function 'main':
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c:40:3: warning: function called through a non-compatible type
((tmp$2)&TEST)( &I$0 );
~^~~~~~~~~~~~~

assembling: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\bin\win32\as.exe --32 --strip-local-absolute "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.asm" -o "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.o"
linking: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\bin\win32\ld.exe -m i386pe -o "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.exe" -subsystem console "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\fbextra.x" --stack 1048576,1048576 -s -L "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32" -L "." "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\crt2.o" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\crtbegin.o" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\fbrt0.o" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.o" "-(" -lfb -lgcc -lmsvcrt -lkernel32 -luser32 -lmingw32 -lmingwex -lmoldname -lgcc_eh "-)" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\crtend.o"
For a test code, see #889 Complex/compact syntax unsupported by gcc
Tourist Trap
Posts: 2642
Joined: Jun 02, 2015 16:24

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby Tourist Trap » Feb 23, 2019 15:18

@PaulSquires,

After compiling, and code stuff has been folded, the position of the carret changes. This means that we don't find back the code in the position left before compilation. This behaviour is probably not wanted.
PaulSquires
Posts: 743
Joined: Jul 14, 2005 23:41
Contact:

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby PaulSquires » Feb 23, 2019 15:49

fxm wrote:The gcc compiler warnings are also not outputted in the "Compiler Result" window:
Successful Compile (Errors 0 Warnings 0)

Primary Source: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.bas
Target Compilation: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.exe (30 Ko
Command Line:
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\fbc32.exe -m "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.bas" "" -v -s console -i ".\FreeBASIC-1.06.0\inc\Afx" -gen gcc

FreeBASIC Compiler - Version 1.06.0 (11-22-2018), built for win32 (32bit)
Copyright (C) 2004-2016 The FreeBASIC development team.
standalone
target: win32, 486, 32bit
compiling: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.bas -o C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c (main module)
compiling C: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\bin\win32\gcc.exe -m32 -march=i486 -S -nostdlib -nostdinc -Wall -Wno-unused-label -Wno-unused-function -Wno-unused-variable -Wno-unused-but-set-variable -Wno-main -Werror-implicit-function-declaration -O0 -fno-strict-aliasing -frounding-math -fno-math-errno -fwrapv -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -masm=intel "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c" -o "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.asm"
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c: In function 'main':
C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.c:40:3: warning: function called through a non-compatible type
((tmp$2)&TEST)( &I$0 );
~^~~~~~~~~~~~~

assembling: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\bin\win32\as.exe --32 --strip-local-absolute "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.asm" -o "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.o"
linking: C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\bin\win32\ld.exe -m i386pe -o "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.exe" -subsystem console "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\fbextra.x" --stack 1048576,1048576 -s -L "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32" -L "." "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\crt2.o" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\crtbegin.o" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\fbrt0.o" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\TMP3145.o" "-(" -lfb -lgcc -lmsvcrt -lkernel32 -luser32 -lmingw32 -lmingwex -lmoldname -lgcc_eh "-)" "C:\Users\fxmam\Documents\Mes Outils Personnels\WinFBE_Suite-1.9.0\FreeBASIC-1.06.0\lib\win32\crtend.o"
For a test code, see #889 Complex/compact syntax unsupported by gcc


Thanks fxm, I have it coded now to capture text outputted after the "compiling: ", and "compiling C:" stages. It is hard to identify what the outputted text relates to because identifiers like #print and #error get lost in the output text. Likewise, identifying that the line is a C compile error is not straightforward. I am now simply just capturing the text and outputting it to lines in the Compiler Output listview.
PaulSquires
Posts: 743
Joined: Jul 14, 2005 23:41
Contact:

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby PaulSquires » Feb 23, 2019 16:18

Tourist Trap wrote:@PaulSquires,

After compiling, and code stuff has been folded, the position of the carret changes. This means that we don't find back the code in the position left before compilation. This behaviour is probably not wanted.


I never use code folding so I have not noticed the problem before. I have modified the code to check if the error line is folded. It will then unfold the block where the error line is located, and then finally goto the error line and highlight it.
Tourist Trap
Posts: 2642
Joined: Jun 02, 2015 16:24

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby Tourist Trap » Feb 23, 2019 16:29

PaulSquires wrote:I never use code folding so I have not noticed the problem before. I have modified the code to check if the error line is folded. It will then unfold the block where the error line is located, and then finally goto the error line and highlight it.

When this is not an error but simply a warning the code tends also to move at the line where the warning is located. Sometimes we will ignore a warning forever so this is not too much a wished behaviour in my opinion.
Thanks for the attention.
Pim Scheffers
Posts: 39
Joined: Jun 29, 2014 17:15

Re: WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (Updated January 22, 2019)

Postby Pim Scheffers » Mar 06, 2019 10:54

Just found this IDE and must say I am pleasantly surprised :-) ... Good work and Thanks!

Return to “Projects”

Who is online

Users browsing this forum: No registered users and 2 guests