Recent

Author Topic: Lazarus Release Candidate 3 for 2.0  (Read 103823 times)

balazsszekely

  • Guest
Re: Lazarus Release Candidate 3 for 2.0
« Reply #60 on: December 31, 2018, 11:52:39 am »
Quote
Maybe we should wait for some feedback first.
OK.

Quote
I think I'll add it to ccr in order to have some workplace if changes are required in the future. It should be clarified here, however, that this VTV4 fork will not be developed any further, I will only fix compilation issues which can creep in sometimes.
I agree. There are too many VTV versions already, it can be confusing.

lucamar

  • Hero Member
  • *****
  • Posts: 4219
Re: Lazarus Release Candidate 3 for 2.0
« Reply #61 on: December 31, 2018, 12:41:44 pm »
Excuse me for changing the topic :P but I need to know:
Will there be any further 2.0 Release Candidates or is this the last one?
Turbo Pascal 3 CP/M - Amstrad PCW 8256 (512 KB !!!) :P
Lazarus/FPC 2.0.8/3.0.4 & 2.0.12/3.2.0 - 32/64 bits on:
(K|L|X)Ubuntu 12..18, Windows XP, 7, 10 and various DOSes.

Thaddy

  • Hero Member
  • *****
  • Posts: 14204
  • Probably until I exterminate Putin.
Re: Lazarus Release Candidate 3 for 2.0
« Reply #62 on: December 31, 2018, 12:45:29 pm »
As always that depends on the test inputs: if there are too many open issues found during testing the RC's will continue, I guess.
That's why it is important to actually use it. Only 'block' issues would qualify.
In general any release candidate is feature complete, so does just need a recompilation with the release.

This isn't off-topic in that sense. A lot of people do not understand where rc's are for: don't ask for features, only for  bug fixes.
« Last Edit: December 31, 2018, 12:55:27 pm by Thaddy »
Specialize a type, not a var.

lucamar

  • Hero Member
  • *****
  • Posts: 4219
Re: Lazarus Release Candidate 3 for 2.0
« Reply #63 on: December 31, 2018, 12:53:04 pm »
Thanks, Thaddy!
Turbo Pascal 3 CP/M - Amstrad PCW 8256 (512 KB !!!) :P
Lazarus/FPC 2.0.8/3.0.4 & 2.0.12/3.2.0 - 32/64 bits on:
(K|L|X)Ubuntu 12..18, Windows XP, 7, 10 and various DOSes.

hubblec4

  • New Member
  • *
  • Posts: 25
Re: Lazarus Release Candidate 3 for 2.0
« Reply #64 on: December 31, 2018, 01:14:51 pm »
@wp and GetMem

Many thanks for investigate your time in VTV to find a solution.

Thaddy

  • Hero Member
  • *****
  • Posts: 14204
  • Probably until I exterminate Putin.
Re: Lazarus Release Candidate 3 for 2.0
« Reply #65 on: December 31, 2018, 02:02:58 pm »
In general this is actually a very good write up: https://en.wikipedia.org/wiki/Software_release_life_cycle
( To my amazement.) Let me quote this:
Quote
Release candidate
A release candidate (RC), also known as "going silver", is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bugs. A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There could still be source code changes to fix defects, changes to documentation and data files, and peripheral code for test cases or utilities. Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product. Beta testing is conducted in a client's or customer's location and to test the software from a user's perspective.
Which is just about what I wrote independently.  8-)
« Last Edit: December 31, 2018, 02:06:28 pm by Thaddy »
Specialize a type, not a var.

avra

  • Hero Member
  • *****
  • Posts: 2514
    • Additional info
Re: Lazarus Release Candidate 3 for 2.0
« Reply #66 on: January 01, 2019, 01:27:26 pm »
I have just downloaded 32-bit FPC 3.0 with latest fixes for Windows, and it still has "No memory left bug" which stops you from installing many components because {$setpeflags $20} fix was not back ported yet.
https://forum.lazarus.freepascal.org/index.php/topic,40351.msg279886.html#msg279886

It would really be a bummer to have official Lazarus 2.0 released without this FPC fix.
ct2laz - Conversion between Lazarus and CodeTyphon
bithelpers - Bit manipulation for standard types
pasettimino - Siemens S7 PLC lib

af0815

  • Hero Member
  • *****
  • Posts: 1289
Re: Lazarus Release Candidate 3 for 2.0
« Reply #67 on: January 01, 2019, 02:02:55 pm »
I didnt see it, because the setpeflags is fixed in fpc fixes 3.2 branch. And my fpcupdeluxe have my patch for older versions.

So i use actually fpc fixes 3.2 & Lazarus fixes 2.0. On Windows, Linux and Raspberry.

I have asked on the fpc mailinglist for Backporting the fix, but no answer. I think it have no priorety/interest for fpc.

Edit: It was Bug 0031517 for the records.
« Last Edit: January 01, 2019, 02:11:36 pm by af0815 »
regards
Andreas

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9792
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 3 for 2.0
« Reply #68 on: January 01, 2019, 02:26:30 pm »
I have just downloaded 32-bit FPC 3.0 with latest fixes for Windows, and it still has "No memory left bug" which stops you from installing many components because {$setpeflags $20} fix was not back ported yet.
https://forum.lazarus.freepascal.org/index.php/topic,40351.msg279886.html#msg279886

It would really be a bummer to have official Lazarus 2.0 released without this FPC fix.

Lazarus 2.0 is going to be released with FPC 3.0.4.

3.0.4 is already released. Fpc backports can either go to fixes 3.0 (i.e. 3.0.5) or fixes 3.2. Neither of this will affect Lazarus 2.0.

But if it is in fixes 3.2, and assuming 3.2 is the next release for fpc, then as soon as 3.2 will be released Lazarus 2.0.x (or 2.2) will include it.

---------------------------
I do recommend that in addition to the official RC (with 3.0.4) everybody should also test Lazarus fixes 2.0 with FPC fixes 3.2 (beta).

If FPC fixes 3.2 is not tested now, then the possibility remains that it may have regression over 3.0.4. And when 3.2 is released everyone will be stuck with the choice between one set of issues, or the other set of issues.
Once 3.2 is release it will (probably) be a long time to 3.2.2 and a long time with any issue that could have been fixed now...

For windows users I created an installer with fixes 3.2. (See the fpc announcement thread here on the forum). For other OS fpcupdeluxe is an option.
« Last Edit: January 01, 2019, 02:32:58 pm by Martin_fr »

avra

  • Hero Member
  • *****
  • Posts: 2514
    • Additional info
Re: Lazarus Release Candidate 3 for 2.0
« Reply #69 on: January 01, 2019, 02:31:46 pm »
setpeflags is fixed in fpc fixes 3.2 branch
Well, official Lazarus is going to come with 3.0.x, so I thought I should lit up a red light on the semaphore. I have little hope anyway, since fix never got back ported to 3.0.x.

And my fpcupdeluxe have my patch for older versions.
FPC 3.0.x fixes branch comes without this fix even in fpcupdeluxe. It needs to be applied manually. I did it by hand and just let fpcupdeluxe rebuild only.
ct2laz - Conversion between Lazarus and CodeTyphon
bithelpers - Bit manipulation for standard types
pasettimino - Siemens S7 PLC lib

avra

  • Hero Member
  • *****
  • Posts: 2514
    • Additional info
Re: Lazarus Release Candidate 3 for 2.0
« Reply #70 on: January 01, 2019, 02:34:50 pm »
3.0.4 is already released. Fpc backports can either go to fixes 3.0 (i.e. 3.0.5) or fixes 3.2. Neither of this will affect Lazarus 2.0.
Thanks for the info. That's a spoiler. Not for me since I know how to fix 'No memory left' bug, but I can already imagine reports from users...
ct2laz - Conversion between Lazarus and CodeTyphon
bithelpers - Bit manipulation for standard types
pasettimino - Siemens S7 PLC lib

af0815

  • Hero Member
  • *****
  • Posts: 1289
Re: Lazarus Release Candidate 3 for 2.0
« Reply #71 on: January 01, 2019, 02:50:49 pm »
Fpc fixes 3.2 testing is important for Lazarus 2.0. Actual i see a issues on arm-plattform , maybe after backporting of some code from trunk into fixes in fpc. So i test / work with the next good platform (for me) - fpc fixes 3.2 with Lazarus fixes 2.0
regards
Andreas

BrunoK

  • Sr. Member
  • ****
  • Posts: 452
  • Retired programmer
Re: Lazarus Release Candidate 3 for 2.0
« Reply #72 on: January 01, 2019, 05:08:13 pm »
1° Has issue 0034763 been fixed in the release candidate ?

2°  Re : NEW FPC VERSION (>3.0.4), has issue
   0033963: Wrong result when a currency variable is multiplied by a constant on windows been fixed ?

Description   
var C: Currency;
begin
  c:= 1000;
  c:= c*1.05;
  // at this point C=1000 instead of 1050
end;
This issue is super dangerous for database software using monetary values, because one could execute a sql batch update and not be concsious it ends with wrong values.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9792
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 3 for 2.0
« Reply #73 on: January 01, 2019, 05:38:26 pm »
1) The issue is still open (assigned). So no it has not yet been fixed.

2) There is a thread about 3.2, which is a better place to discuss fpc 3.2 issues. (As they go to the fpc team)

mmvisual

  • New Member
  • *
  • Posts: 19
Re: Lazarus Release Candidate 3 for 2.0
« Reply #74 on: January 01, 2019, 05:55:53 pm »
Hello,

I have install the new Lazarus rc3. After compile my source, start the EXE, it crashes directly.

I write in the German forum the, but my english is not so good:
http://www.lazarusforum.de/viewtopic.php?p=107046#p107046

Best regards, Markus

PS: I'm the one from the million  :D
« Last Edit: January 01, 2019, 05:59:03 pm by mmvisual »

 

TinyPortal © 2005-2018