[fpc-devel] [patch] - readme for tests in 'cpstrnew' branch

Hi, Attached is a patch for the readme file in the tests directory. Needs to be applied against the 'cpstrnew' branch. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

[fpc-devel] debugging the RTL (system unit)

Hello, How I can debug problems with the system and rtl in general for the reason my code crashes before it execute my own code ? Thanks, Ido http://ik.homelinux.org/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org

Re: [fpc-devel] debugging the RTL (system unit)

On Thu, December 3, 2009 12:21, ik wrote: Hello, How I can debug problems with the system and rtl in general for the reason my code crashes before it execute my own code ? You can certainly build the RTL with debug information (I believe that make debug in the RTL directory should do that)

Re: [fpc-devel] debug information for Variant type

On 01 Dec 2009, at 13:42, Paul Ishenin wrote: Jonas Maebe wrote: Would it be enough if the type name were changed to variant? It would not be 100% safe (since variant is not a reserved word, anyone can declare a variable/type/... with the name variant), but I don't immediately see

Re: [fpc-devel] debug information for Variant type

Jonas Maebe wrote: On 01 Dec 2009, at 13:42, Paul Ishenin wrote: Jonas Maebe wrote: Would it be enough if the type name were changed to variant? It would not be 100% safe (since variant is not a reserved word, anyone can declare a variable/type/... with the name variant), but I don't

[fpc-devel] test cases in FPC - how to they work?

hi, I'm working on Linux support for code page enabled string types (branch cpstrnew). In general, is their a special way that the test projects in 'fpc/tests/test/*' should be run? Sorry, I'm used to FPCUnit or DUnit2 test cases which gives a clear indication if a test passed or failed.

Re: [fpc-devel] debug information for Variant type

On 03 Dec 2009, at 14:29, Marc Weustink wrote: Jonas Maebe wrote: On 01 Dec 2009, at 13:42, Paul Ishenin wrote: Jonas Maebe wrote: Would it be enough if the type name were changed to variant? It would not be 100% safe (since variant is not a reserved word, anyone can declare a

Re: [fpc-devel] test cases in FPC - how to they work?

On 03 Dec 2009, at 14:31, Graeme Geldenhuys wrote: In general, is their a special way that the test projects in 'fpc/tests/test/*' should be run? From fpc/tests/readme.txt: *** Writing a test -- A test should have a name on the form t*.pp, to be recognized as a test. It should

Re: [fpc-devel] debug information for Variant type

Jonas Maebe wrote: On 03 Dec 2009, at 14:29, Marc Weustink wrote: Jonas Maebe wrote: On 01 Dec 2009, at 13:42, Paul Ishenin wrote: Jonas Maebe wrote: Would it be enough if the type name were changed to variant? It would not be 100% safe (since variant is not a reserved word, anyone can

Re: [fpc-devel] test cases in FPC - how to they work?

Jonas Maebe wrote: A test should have a name on the form t*.pp, to be recognized as a test. It should return 0 on success, any other value indicates failure. Ah thanks! And that would explain the lines with Halt(1) at the end of those test projects :-) No idea how I missed that. :-(

Re: [fpc-devel] debug information for Variant type

On 03 Dec 2009, at 15:09, Marc Weustink wrote: Jonas Maebe wrote: It's also possible to create another definition of tvarrec with variant as name. In that case I think I prefer a full dwarf variant :) Ok, it's now called Variant. As an extra advantage, I think that this cannot clash

[fpc-devel] [PATCH] cpstrnew: fixed spelling mistake in record name

Patch needs to be applied against branch 'cpstrnew'. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ 0001-Fixed-spelling-mistake-in-TEncodingEntry-record.patch Description: application/mbox

[fpc-devel] where should patches for branches go?

Hi, I sent two patches for the 'cpstrnew' branch to the mailing list because FPC's Mantis doesn't have a category or sub-project for branches. Is it ok if I continue sending them here, or is there a specific place in Mantis I should place them? -- Regards, - Graeme -

Re: [fpc-devel] debug information for Variant type

Jonas Maebe wrote: Ok, it's now called Variant. As an extra advantage, I think that this cannot clash with user-defined types, because afaik those type names are always uppercased. Thanks. This is what I asked. Can it be similar for STABS? Best regards, Paul Ishenin.

[fpc-devel] rtl/arm/thumb2.inc vs rtl/arm/arm.inc

Hello, What is the difference between thumb2.inc and arm.inc ? Thanks, Ido http://ik.homelinux.org/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] error when crosscompile for arm

On 02 Dec 2009, at 18:06, Dariusz Mazur wrote: Jonas Maebe pisze: The reason is because x87 fpu supports a signed 64 bit integer type (which Borland called comp). They introduced that type to allow people to perform fairly quick 64 bit arithmetic mathematics on the old Intel 16 bit

Re: [fpc-devel] where should patches for branches go?

On 03 Dec 2009, at 16:33, Graeme Geldenhuys wrote: I sent two patches for the 'cpstrnew' branch to the mailing list because FPC's Mantis doesn't have a category or sub-project for branches. Is it ok if I continue sending them here, or is there a specific place in Mantis I should place them?