Re: [fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-17 Thread Michael Van Canneyt
On Tue, 17 Jul 2012, Seth Grover wrote: Also, it looks like it gets a segfault if you try to $include a file that can't be found. Fixed in rev. 21932. Uninitialized result. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http:

Re: [fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-17 Thread Michael Van Canneyt
On Tue, 17 Jul 2012, Seth Grover wrote: I ran into another problem scenario, dealing with $include'd files. Given these two files: I get an error like this: Syntax error at token "EOF" in file iputils.pas at line 21 column -7202378 line:21 column:-7202378 file:iputils.pas Fixed. Undefine

Re: [fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-17 Thread Michael Van Canneyt
On Mon, 16 Jul 2012, Seth Grover wrote: I should have fixed both problems you found. Please test, rev 21922. Michael. It did fix those problems, but there's still a problem in the release given the following unit with a finalization section: === unit

Re: RE : [fpc-pascal] Database problem on Solaris SPARC

2012-07-17 Thread Reinier Olislagers
On 17-7-2012 22:20, Mark Morgan Lloyd wrote: > Mark Morgan Lloyd wrote: >> Sven Barth wrote: >> > Now, you are getting a SIGSEGV, not a SIGBUS which is what you would > get for > an alignment problem. This problem no longer exists in 2.7.1 (21919 + Reinier's solarisdbtrun

Re: RE : [fpc-pascal] Database problem on Solaris SPARC

2012-07-17 Thread Mark Morgan Lloyd
Mark Morgan Lloyd wrote: Sven Barth wrote: Now, you are getting a SIGSEGV, not a SIGBUS which is what you would get for an alignment problem. This problem no longer exists in 2.7.1 (21919 + Reinier's solarisdbtrunk2.diff). Then it might be good if you report this in Mantis together with Re

[fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-17 Thread Seth Grover
Also, it looks like it gets a segfault if you try to $include a file that can't be found. -SG -- This email is fiction. Any resemblance to actual events or persons living or dead is purely coincidental. Seth Grover ___ fpc-pascal maillist - fpc-pasca

[fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-17 Thread Seth Grover
I ran into another problem scenario, dealing with $include'd files. Given these two files: ==iputils.pas unit iputils; {$mode objfpc}{$H+} interface {$define IPv6_Types} {$include ip.inc} {$undef IPv6_Types} {$define IPv6_Interface} {$in

Re: RE : [fpc-pascal] Database problem on Solaris SPARC

2012-07-17 Thread Mark Morgan Lloyd
Sven Barth wrote: Now, you are getting a SIGSEGV, not a SIGBUS which is what you would get for an alignment problem. This problem no longer exists in 2.7.1 (21919 + Reinier's solarisdbtrunk2.diff). Then it might be good if you report this in Mantis together with Reinier's patch so that it i

Re: RE : [fpc-pascal] Database problem on Solaris SPARC

2012-07-17 Thread Sven Barth
Am 17.07.2012 11:12, schrieb Mark Morgan Lloyd: Ludo Brands wrote: We only support 32 bit SPARC, and there we split a 64 bit load into two 32 bit loads. dbl, assuming it points to a double, should point to a 64 bit-aligned memory location though (depending on the cpu, 32 bit alignment may be s

Re: [fpc-pascal] Variable of class method type of function

2012-07-17 Thread Bernd K.
On 17.07.2012 01:09, waldo kitty wrote: > now we need to remember to use "of object" when we are working with nothing > but > classes? Imagine for a moment (in a parallel universe) there exists no keyword "object" and never has. All there has ever been was the keyword "class". now you have ty

Re: RE : [fpc-pascal] Database problem on Solaris SPARC

2012-07-17 Thread Mark Morgan Lloyd
Ludo Brands wrote: We only support 32 bit SPARC, and there we split a 64 bit load into two 32 bit loads. dbl, assuming it points to a double, should point to a 64 bit-aligned memory location though (depending on the cpu, 32 bit alignment may be sufficient, but better be safe than sorry). I'll