Re: out vs. var (was: Re: [fpc-devel] Internal error in FPC 2.6.0rc1)

2011-11-29 Thread Michael Müller
Am 28.11.2011 um 13:12 schrieb Jonas Maebe: > > On 28 Nov 2011, at 12:02, Michael Müller wrote: > >> Am 28.11.2011 um 01:05 schrieb Jonas Maebe: >> >>> If you enable hints, the compiler will print a hint if it detects you >>> passing a potentially unin

Re: out vs. var (was: Re: [fpc-devel] Internal error in FPC 2.6.0rc1)

2011-11-28 Thread Michael Müller
Am 28.11.2011 um 01:05 schrieb Jonas Maebe: > > On 28 Nov 2011, at 00:49, Michael Müller wrote: > >> Beside that what is than the difference between 'out' and 'var'? > > If you enable hints, the compiler will print a hint if it detects you passing &g

out vs. var (was: Re: [fpc-devel] Internal error in FPC 2.6.0rc1)

2011-11-27 Thread Michael Müller
Hi Sergei Am 25.11.2011 um 13:49 schrieb Sergei Gorelkin: > 25.11.2011 13:36, Michael Müller пишет: >> Hi, >> >> I tested RC1 using one of my codes and ran into an internal error. I was >> able to reduce the code to the following. >> >> Free Pascal Com

[fpc-devel] Internal error in FPC 2.6.0rc1

2011-11-25 Thread Michael Müller
Hi, I tested RC1 using one of my codes and ran into an internal error. I was able to reduce the code to the following. Free Pascal Compiler version 2.6.0rc1 [2011/10/15] for i386 Copyright (c) 1993-2011 by Florian Klaempfl and others Target OS: Win32 for i386 Compiling InternalError.dpr Internal

Re: [fpc-devel] Purpose of "uses ... in"?

2010-07-11 Thread Michael Müller
Am 11.07.2010 um 19:48 schrieb Daniël Mantione: > Op Sun, 11 Jul 2010, schreef Hans-Peter Diettrich: > >> I know that the "in " is part of the Delphi syntax, but what is it >> really good for? > > In my opinion, it is not usefull. I have never seen a clear description of > what the semantics

[fpc-devel] Free Pascal V1.0.10

2008-09-01 Thread Michael Müller
Hi, before we will start to add QNX support to the recent version of Free Pascal we need for an old project for the developers under Windows to check that our code stays V1.0.10 compilable under QNX the Windows/ DOS version of V1.0.10. Several weeks ago I found it listed under http://www.f

Re: [fpc-devel] FreePascal for QNX

2008-07-21 Thread Michael Müller
Hi Florian! Am 18.07.2008 um 14:26 schrieb Florian Klaempfl: Marco van de Voort schrieb: Now this topic came back to my attention. So before we will start our work I want to ask some questions. Did in the meantime perhaps somebody already started to add QNX as a target? Afaik 1.0.x h

Re: [fpc-devel] FreePascal for QNX

2008-07-20 Thread Michael Müller
Hi Marco, thanks for the anwser. Am 18.07.2008 um 11:08 schrieb Marco van de Voort: Can somebody make an estimation (in man month) how long it could take? A skilled person could probably do a basic port to a unix target in a handful of evenings. Your effort estimation sounds promising alth

[fpc-devel] FreePascal for QNX

2008-07-18 Thread Michael Müller
Hi, I already posted a question related to this topic two years ago: http://community.freepascal.org:1/lists/fpc-pascal/2006-February/ 010111 Now this topic came back to my attention. So before we will start our work I want to ask some questions. Did in the meantime perhaps somebody a

[fpc-devel] SSE operation addps doesn't work in subroutine

2008-01-12 Thread Michael Müller
Hi, today I tried to use SSE operations. But I couldn't get what I want. Here is a simple code: program SSETestsSimple; {$mode objfpc}{$H+} {$ALIGN 16} uses SysUtils, MMX; type TSSESingle = array[0..3] of Single; {$ASMMODE ATT} procedure SSEAdd(const v1, v2: TSSESingle; out v_r: TSS

Re: [fpc-devel] Mutex!

2006-11-05 Thread Michael Müller
Am 05.11.2006 um 12:14 schrieb Colin Western: Amir Aavani wrote: InitCriticalSection (cs); while true do begin EnterCriticalsection (cs); WriteLn ('Here!'); end; LeaveCriticalsection (cs); Each Enter.. must be matched by a Leave..., and you don't need the loop. The standard wa

Re: [fpc-devel] FPC compiles malformed code

2006-08-24 Thread Michael Müller
Am 24.08.2006 um 04:04 schrieb Graeme Geldenhuys: Maybe because pascal is insensitive to whitespace between tokens. You also can write: lData.Name:='Graeme'; and lData.Name := 'Graeme'; I understood that as: between the symbols etc... eg; := or = or , Never thought that would mean betw