FBC 1.00.0

General discussion for topics related to the FreeBASIC project or its community.
dodicat
Posts: 7976
Joined: Jan 10, 2006 20:30
Location: Scotland

Re: FBC 1.00.0

Post by dodicat »

Thanks St_W
I had sifted through line endings also, but missed the #define ending.

Either we must type very strictly #defines() --- or use #macro() --- #endmacro instead.

Thank you for all these auto builds.
fxm
Moderator
Posts: 12081
Joined: Apr 22, 2009 12:46
Location: Paris suburbs, FRANCE

Re: FBC 1.00.0

Post by fxm »

Well done St_W!

Yes adding a trailinge space at the end of the #define line induces the compiler error, but only with fbc version 1.01.0:
- compilation OK for fbc_win32_mingw_0155_2014-09-27.zip 27-Sep-2014 02:09
- compilation NOK for fbc_win32_mingw_0157_2014-09-27.zip 28-Sep-2014 02:00

This revolves around 27-Sep-2014, but I have not found the change that can induce this bad behavior!
St_W
Posts: 1618
Joined: Feb 11, 2009 14:24
Location: Austria
Contact:

Re: FBC 1.00.0

Post by St_W »

fxm wrote:Yes adding a trailinge space at the end of the #define line induces the compiler error, but only with fbc version 1.01.0:
- compilation OK for fbc_win32_mingw_0155_2014-09-27.zip 27-Sep-2014 02:09
- compilation NOK for fbc_win32_mingw_0157_2014-09-27.zip 28-Sep-2014 02:00

This revolves around 27-Sep-2014, but I have not found the change that can induce this bad behavior!
That's already a very good discovery. I tried both build #155 (2014-09-27 01:56:57) and build #156 (2014-09-27 03:41:59) and the latter introduced the compiler error. Thus it's probably something from these two commits: However, one other possible source of the problem might also be my build. For example always the same fbc version is used to compile fbc - meanwhile this version (a 0.91 git compile from somewhere around february this year) is already quite old and may contain a bug which would be already fixed in a newer version. This fbc installation on the Jenkins server is currently not updated automatically, but has to be updated manually.
That's only one possible reason and there are probably a lot of such reasons, that I currently can't think of.

So now it's dkl's turn :-)

(btw: #156 was not uploaded to freebasic-portal, as only the latest build each morning at 02:00 (GMT+1) is uploaded for space reasons)
fxm
Moderator
Posts: 12081
Joined: Apr 22, 2009 12:46
Location: Paris suburbs, FRANCE

Re: FBC 1.00.0

Post by fxm »

St_W wrote:So now it's dkl's turn :-)
@Admin:
Should we file a bug report for that?
(I can do it)
counting_pine
Site Admin
Posts: 6323
Joined: Jul 05, 2005 17:32
Location: Manchester, Lancs

Re: FBC 1.00.0

Post by counting_pine »

Good idea.
fxm
Moderator
Posts: 12081
Joined: Apr 22, 2009 12:46
Location: Paris suburbs, FRANCE

Re: FBC 1.00.0

Post by fxm »

dkl
Site Admin
Posts: 3235
Joined: Jul 28, 2005 14:45
Location: Germany

Re: FBC 1.00.0

Post by dkl »

Thanks for figuring out the test case that triggered the problem, it was most useful. The problem should be fixed in Git now. Apparently the macro recursion check was broken in combination with parser look-ahead, which is used more extensively since the recent changes in fbc 1.01 expression parsing.
MrSwiss
Posts: 3910
Joined: Jun 02, 2013 9:27
Location: Switzerland

Re: FBC 1.00.0

Post by MrSwiss »

May be a bit offtopic:
The idea of releasing more often, warmed up again ...

Would it be to big an effort to: release a "bug-fixed" fbc (and maybe fixed "main" lib's,
like fbgfx) at a rate of let's say a 3 month frame, because not everybody here is comfy
with dev-builds ...

As a side effect, the recent changes whould be "more extensively" tested, too.
Post Reply