Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-21 Thread Santiago A.
El 19/11/2017 a las 11:06, Adriaan van Os escribió: > Mark Morgan Lloyd wrote: > >> That obviously applies to all languages, I've never come across >> something which can represent 1/3 or pi exactly. > > If you do read what is written in the link - that is not the issue. > The issue is how to

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-20 Thread Mark Morgan Lloyd
On 20/11/17 12:00, Schindler Karl-Michael wrote: Am 20.11.2017 um 12:00 schrieb fpc-pascal-requ...@lists.freepascal.org:> > Date: Sun, 19 Nov 2017 11:14:50 +> From: Mark Morgan Lloyd <markmll.fpc-pas...@telemetry.co.uk>> To: fpc-pascal@lists.freepascal.org> Subject: Re:

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-20 Thread Schindler Karl-Michael
> Am 20.11.2017 um 12:00 schrieb fpc-pascal-requ...@lists.freepascal.org: > > Date: Sun, 19 Nov 2017 11:14:50 + > From: Mark Morgan Lloyd <markmll.fpc-pas...@telemetry.co.uk> > To: fpc-pascal@lists.freepascal.org > Subject: Re: [fpc-pascal] FORTRAN from FreePascal >

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-19 Thread Adriaan van Os
Mark Morgan Lloyd wrote: Oh really? Well I'll let you travel back in time and argue with numerous former colleagues who've routinely found differences between their "fortran" (-IV, -77 or whatever) and "fast fortran" compilers which in those days tended to be separate programs even if

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-19 Thread Adriaan van Os
Mark Morgan Lloyd wrote: I read the link before posting. You aren't going to represent 1/3 or Pi exactly in BCD either. Again, that is not the point. Read the technical docs before posting. Adriaan van Os ___ fpc-pascal maillist -

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-19 Thread Mark Morgan Lloyd
On 19/11/17 12:15, Bo Berglund wrote: On Sun, 19 Nov 2017 11:14:50 +, Mark Morgan Lloyd wrote: I think we're in broad agreement though: don't try converting backend >code unless you know exactly what you're doing, and Pascal (including >Lazarus/LCL

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-19 Thread Bo Berglund
On Sun, 19 Nov 2017 11:14:50 +, Mark Morgan Lloyd wrote: >I think we're in broad agreement though: don't try converting backend >code unless you know exactly what you're doing, and Pascal (including >Lazarus/LCL etc.) can be valuable when implementing a

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-19 Thread Mark Morgan Lloyd
On 19/11/17 10:15, Adriaan van Os wrote: Mark Morgan Lloyd wrote: That obviously applies to all languages, I've never come across > something which can represent 1/3 or pi exactly. If you do read what is written in the link - that is not the issue. The issue is how to interpret floating-point

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-19 Thread Adriaan van Os
Mark Morgan Lloyd wrote: That obviously applies to all languages, I've never come across something which can represent 1/3 or pi exactly. If you do read what is written in the link - that is not the issue. The issue is how to interpret floating-point constants and how to convert

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-19 Thread Mark Morgan Lloyd
On 19/11/17 04:00, Adriaan van Os wrote: Mark Morgan Lloyd wrote:> I think that conventional wisdom is that if somebody's written numerical > analysis code you don't change it gratuitously, since any alterations > will change rounding errors etc. For some reason, that seems to apply >

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread Adriaan van Os
Mark Morgan Lloyd wrote: I think that conventional wisdom is that if somebody's written numerical analysis code you don't change it gratuitously, since any alterations will change rounding errors etc. For some reason, that seems to apply particularly to FORTRAN programs :-) The reason being

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread Adriaan van Os
Mark Morgan Lloyd wrote: Except that when you're calling into a DLL (.so on Linux etc.) I don't think you have much chance of seeing the inside of the library code. On Mac OS X, which is actually a BSD UNIX, I debug plug-in code all the time. Not an issue at all. Regards, Adriaan van Os

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread pascalX
On 18/11/17 20:14, Mark Morgan Lloyd wrote: I think that conventional wisdom is that if somebody's written numerical analysis code you don't change it gratuitously, since any alterations will change rounding errors etc. For some reason, that seems to apply particularly to FORTRAN programs :-)

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread Mark Morgan Lloyd
On 18/11/17 19:45, Bo Berglund wrote: On Sat, 18 Nov 2017 17:06:25 +, Mark Morgan Lloyd wrote: I find myself wondering, in part due to conversations elsewhere: can the >Lazarus IDE do anything at all sane with a FORTRAN routine called from >Pascal? In

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread Bo Berglund
On Sat, 18 Nov 2017 17:06:25 +, Mark Morgan Lloyd wrote: >I find myself wondering, in part due to conversations elsewhere: can the >Lazarus IDE do anything at all sane with a FORTRAN routine called from >Pascal? In the D7 application written in

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread Adriaan van Os
Mark Morgan Lloyd wrote: I find myself wondering, in part due to conversations elsewhere: can the Lazarus IDE do anything at all sane with a FORTRAN routine called from Pascal? It's not different from a call to C or any other compiled language. And with regard to debugging, I think it will

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread Mark Morgan Lloyd
On 18/11/17 16:45, Adriaan van Os wrote: Bo Berglund wrote: I would very much want to convert them into DLL:s programmed in Pascal> instead so they can be maintained for new Windows versions (and use 64> bit for example). Well, you would have to do that by hand. And you need sufficient

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-18 Thread Adriaan van Os
Bo Berglund wrote: I would very much want to convert them into DLL:s programmed in Pascal instead so they can be maintained for new Windows versions (and use 64 bit for example). Well, you would have to do that by hand. And you need sufficient understanding of Fortran to know what you are

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-17 Thread Schindler Karl-Michael
> Am 17.11.2017 um 12:00 schrieb fpc-pascal-requ...@lists.freepascal.org: > > Date: Thu, 16 Nov 2017 20:50:57 -0500 > From: Bo Berglund <bo.bergl...@gmail.com> > To: fpc-pascal@lists.freepascal.org > Subject: Re: [fpc-pascal] FORTRAN from FreePascal > Message-ID: <l

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-16 Thread Bo Berglund
On Sun, 12 Nov 2017 08:56:49 -0500, brian wrote: >Anyone with any past experience here? It seems I have two choices, to >try to call the FORTRAN subroutines from FreePascal or to port the >FORTRAN code to Pascal, I'm looking for advice... I have a similar problem, a

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-13 Thread brian
On 11/13/2017 10:20 AM, Adriaan van Os wrote: > brian wrote: >> Anyone with any past experience here? It seems I have two choices, to >> try to call the FORTRAN subroutines from FreePascal or to port the >> FORTRAN code to Pascal, I'm looking for advice... > > It is no problem calling FORTRAN

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-13 Thread Adriaan van Os
brian wrote: Anyone with any past experience here? It seems I have two choices, to try to call the FORTRAN subroutines from FreePascal or to port the FORTRAN code to Pascal, I'm looking for advice... It is no problem calling FORTRAN from either C or FreePascal (or at least not on UNIX-like

Re: [fpc-pascal] FORTRAN from FreePascal

2017-11-13 Thread Mark Morgan Lloyd
On 13/11/17 13:30, brian wrote: I need to try to put a user-friendly GUI and some graphical outputonto an old command-line FORTRAN number cruncher, and have beenprovided with around 130 KB of FORTRAN source code. A quick scan ofdocumentation seems to suggest that this is possible using

[fpc-pascal] FORTRAN from FreePascal

2017-11-13 Thread brian
I need to try to put a user-friendly GUI and some graphical output onto an old command-line FORTRAN number cruncher, and have been provided with around 130 KB of FORTRAN source code. A quick scan of documentation seems to suggest that this is possible using gfortran and the C calling conventions