Re: [fpc-pascal] New package to evaluate Pascal-expressions

2020-10-24 Thread C Western via fpc-pascal

On 21/10/2020 16:57, Joost van der Sluis via fpc-pascal wrote:


Hi all,

Working on fpDebug, I've got onto a side-track and created an 
expression-evaluator based on fcl-passrc 
. So that you can 
evaluate Pascal-expressions at runtime.


Regards,

In the hope this will encourage work on fpDebug, I attach modifications 
that will allow it to work with floating point values, including a 
selection of the RTL functions.


Colin



mods.tgz
Description: application/compressed-tar
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Re: [fpc-pascal] Access Violation on second compile with FPC Text IDE

2020-11-12 Thread C Western via fpc-pascal

On 11/11/2020 22:26, James Richters via fpc-pascal wrote:

I'm suddenly getting an access violation when compiling after a file changed 
with the FPC text IDE:

Recompiling because of I:\Programming\Gcode\Mill\pastep.pas
sysinit.pp(0) Error: Compilation raised exception internally
Error: Compiler exited
Error: Access violation

I haven't changed anything as far as FPC goes, and I'm using the same procedure 
I always have.. I make my edits in notepad++ then go to the text IDE and 
compile it.. it detects which files changed and re-compiles those.. it normally 
works fine, but now I am always getting this.  I restart the text IDE and 
compile it and run it and it's fine.. no problems, I make even a minor change, 
and try to re-compile it and bam I get this access violation error.  Does 
anyone know what this error actually means or how to track it down?

  James

Is this with a recent trunk? I have started seeing this recently; an 
interface change in one unit causes a crash when compiling another unit. 
The workaround is to force recompilation of everything, which I do by 
deleting all the compiled files for the program. It is tricky to report 
as a bug, as it is intermittent, and I have only seen it on a large program.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Re: [fpc-pascal] Abstract classes ignored

2021-04-18 Thread C Western via fpc-pascal

On 18/04/2021 03:34, Ryan Joseph via fpc-pascal wrote:



On Apr 17, 2021, at 3:09 PM, Sven Barth  wrote:

The compiler will generate a warning in case you instantiate a class that is 
abstract or has abstract methods. You can escalate these warnings to errors if 
you need:

It's probably not practical to put that warning into all potential files but a 
warning is still probably good enough as a reminder. It's curious though why 
it's not an error by default, because if the class is abstract and you 
instantiate it and try to use it things are going to fail anyways so why does 
the compiler allow it in the first place?

Regards,
Ryan Joseph

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


My own code will have cases where I have only implemented some of the 
abstract methods for some classes, in principle because the code is 
incomplete, but there are also case where it never makes sense to 
implement them and calling them indicates a logical error elsewhere in 
the code.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal