On Sat, 15 Sep 2012 11:20:53 +0200, Sven Barth
wrote:
On 14.09.2012 17:44, Graeme Geldenhuys wrote:
On 14/09/12 13:48, Krzysztof wrote:
I just quicky googled not allowed characters and wrote this simple
function:
Also in Windows (as far as I know), file names my not be longer than 255
cha
On Fri, 14 Sep 2012 18:53:53 +0200, Krzysztof wrote:
I need only basic checking, it not need to be 100% compability with OS
specification. My program asking user for playlist name and I'm saving
it in local folder with my own extension.
Then for von Neumanns sake simply try to save it where t
On Fri, 14 Sep 2012 18:42:55 +0200, Jorge Aldo G. de F. Junior
wrote:
am i the only one seeing a security risk here ?
Now it dawns. You're thinking environment variables ("%")?
Vinzent.
--
The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where
On Fri, 14 Sep 2012 18:42:55 +0200, Jorge Aldo G. de F. Junior
wrote:
am i the only one seeing a security risk here ?
*scratching head* Which part? Care to elaborate?
I'd presume, you mean another than that I'm using Windows? ;)
I don't see how manually restricting the character set of an
On Fri, 14 Sep 2012 14:48:08 +0200, Krzysztof wrote:
I just quicky googled not allowed characters and wrote this simple
function:
Seems, you found one of the many (I'd suspect) wrong search results.
function IsValidFilename(const AFilename: String): Boolean;
var
c: set of Char = ['<','>'
On Wed, 12 Sep 2012 20:44:21 +0200, Jonas Maebe
wrote:
Include an appropriate {$packenum xxx} directive in your source code.
There is no {$packenum c} (I'm not even sure whether the C standard says
anything about the size of enums),
Yes, it does say something about it:
|Each enumerated
On Sat, 25 Feb 2012 19:15:54 +0100, ik wrote:
I found the following amazing lecture that present a new idea of a
development tool, that I think will interest you all:
http://vimeo.com/36579366
Impressive, indeed. And I am usually not that easily impressed.
Vinzent.
On Fri, 20 Jan 2012 21:38:04 +0100, kingbiz...@gmail.com
wrote:
I would like to know if is there any way to get the time in a high
precision, something like nannoseconds.
Yes. Depending on the required resolution, the operating system, processor
architecture, and your portability requirement
On Mon, 02 Jan 2012 15:12:15 +0100, luciano de souza
wrote:
So I ask: Does someone know a commandline tool that indents the code
automatically?
Try 'ptop'. It comes with FPC already.
Vinzent.
___
fpc-pascal maillist - fpc-pascal@lists.freepasc
On Thu, 08 Dec 2011 10:52:01 +0100, Graeme Geldenhuys
wrote:
On 8 December 2011 11:33, Henry Vermaak wrote:
I agree, quality first.
I would normally agree with that. But such huge magnitudes slower
(20ms vs 10585ms) on a new Quad-Core type system? That just seems a
bit excessive, and con
On Sat, 21 May 2011 13:19:35 +0200, Rainer Stratmann
wrote:
Am Saturday 21 May 2011 12:21:54 schrieb Mattias Gaertner:
They are typical dpkg messages. This is pretty normal when installing
deb packages manually. That is not specific to Lazarus or FPC.
The problem is that the tar contains *a
On Tue, 01 Mar 2011 12:38:27 +0100, Michael Fuchs
wrote:
I also miss a NotImplementedException (or ENotImplemented in FPC style),
very handy for test driven development. :)
Yeah. And
type
//-- @abstract(Obvious coding error.)
Coder_Needs_Coffee = class (SysUtils.Exception);
was ver
On Sun, 21 Nov 2010 20:35:42 +0100, Michael Müller
wrote:
Single has 7 significant digits.
Six significant digits. The seventh already is unreliable.
Vinzent.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.or
On Sun, 21 Nov 2010 18:54:13 +0100, Helmut Hartl
wrote:
Running the above program gives
1) C++ / FPC 64 Bit
6.3846106530
6.3846106530
2) FPC32 Bit
6.3846106530
6.3846111610
Is this explainable or wrong behaviour ?
First suspect candidate: the intermediate results are calculated wit
On Fri, 19 Nov 2010 23:02:11 +0100, Cox, Stuart TRAN:EX
wrote:
I think the easiest way to get cross-platform lockfile behaviour, is to
a) create the lockfile at the start of your program (e.g., a rewrite
followed by a close)
b) whenever you want to lock it, use
systutils.fileopen(lockfilenam
On Tue, 02 Nov 2010 21:39:31 +0100, Felipe Monteiro de Carvalho
wrote:
On Tue, Nov 2, 2010 at 7:04 PM, Bo Berglund
wrote:
Thanks, that helps a lot! Are there also overloaded BEtoN functions
for floating point values?
I think that single and double have always the same binary layout.
Mo
On Tue, 19 Oct 2010 02:07:25 +0200, Dimitri Smits
wrote:
on the other hand, what stops the OP from using 'with'? (multiple
levels/variables?)
"with" contaminates the name space. Locally scoped variables don't.
and you won't die from using another stack variable scoped at the
beginning of
On Sat, 16 Oct 2010 18:04:59 +0200, Luca Olivetti wrote:
I use that only for threads I start at the beginning of the app and
terminate at the end, so polling isn't a big issue.
Those kind of threads are not a big issue at all. As they are running
during the whole application's lifetime, race
On Sat, 16 Oct 2010 17:42:03 +0200, Luca Olivetti wrote:
Al 16/10/10 16:57, En/na Vinzent Höfler ha escrit:
Well, the usual implementation of an externally called "Destroy" is
- first a call to the Terminate method
- then a WaitFor()
Nope, I avoid the WaitFor.
Nice for yo
On Sat, 16 Oct 2010 17:12:51 +0200, Jonas Maebe
wrote:
On 16 Oct 2010, at 17:13, Martin Schreiber wrote:
As written before it does not crash in
tmsethread which does not inherit from FPC TThread.
You're just getting lucky in your tests.
Either that, or the object validity checks are off
On Sat, 16 Oct 2010 10:45:49 +0200, Luca Olivetti wrote:
Al 15/10/10 22:31, En/na Vinzent Höfler ha escrit:
- FreeOnTerminate should be gone, (meaning no way to actively call
TThread.Destroy from another thread, a thread gets destroyed
automatically when it leaves its execute method)
I
On Sat, 16 Oct 2010 00:17:33 +0200, Marco van de Voort
wrote:
In our previous episode, Vinzent H?fler said:
Hmm. Actually, I did not think too hard about it yet.
So for a quick brainstorming approach:
- Suspend/Resume should be gone (you can't guarantee it to work,
so there's no point i
On Fri, 15 Oct 2010 23:41:36 +0200, Andrew Brunner
wrote:
Do you have a link to the latest version of pthreads?
You probably mean NPTL (Native Posix Threading Library).
It was my understanding that libc took over the pthreads project. I
just took up this issue a few days ago so I recogni
On Fri, 15 Oct 2010 22:50:29 +0200, Jonas Maebe
wrote:
On 15 Oct 2010, at 22:31, Vinzent Höfler wrote:
- Suspend/Resume should be gone (you can't guarantee it to work,
so there's no point in doing it at all)
FWIW, they're deprecated since Delphi 2009, so they will disapp
On Fri, 15 Oct 2010 22:13:36 +0200, Sven Barth
wrote:
I'm curious. How should this FPThread class look like? You saw flaws in
Delphi's API so what would you do better?
Hmm. Actually, I did not think too hard about it yet.
So for a quick brainstorming approach:
- Suspend/Resume should be
On Fri, 15 Oct 2010 18:26:59 +0200, Andrew Brunner
wrote:
Externally suspending a thread *IS* absolutely unsafe.
At least we're on the same page here. :)
But the notion of suspending an ENGINE at runtime externally is
totally expected.
The thread itself MUST put itself in a suspended state.
On Fri, 15 Oct 2010 20:15:51 +0200, Andrew Brunner
wrote:
On Fri, Oct 15, 2010 at 12:01 PM, Vinzent Höfler
wrote:
Exactly. It was poor implementation. You should have had a global
barrier onExecute. That would unlock the thread after everything you
needed was readable.
If it's g
On Fri, 15 Oct 2010 18:19:14 +0200, Andrew Brunner
wrote:
On Fri, Oct 15, 2010 at 10:57 AM, Vinzent Höfler
wrote:
If you access it inside the execute method, you more or
less crash (or at least leak memory).
You obviously had a problem with access ThreadID before it was assigned
On Fri, 15 Oct 2010 17:39:59 +0200, Andrew Brunner
wrote:
BTW: I did notice that the semaphore was being used to suspend the
thread. And I also know that that was it's only function... Suspend
and Resume.
The problem is not pthreads or anything, the problem is how the
semantics of the Classe
On Fri, 15 Oct 2010 16:45:04 +0200, Andrew Brunner
wrote:
It was also suggested that PThread's Suspend and Resume may not do
anything. What I would do (if that is the case), is try to find where
PThread has access to the Semaphore or CriticalSection it has on that
thread...
Huh? Why should
Marcos Douglas :
> > But then, IME (most) name conflicts are a sure sign of inproper names.
> Take the
> > example of "constants.pas": What sort of constants shall I expect there?
> Screen sizes,
> > color codes, electron mass or the gravitational constant?
>
> You right about "constants.pas".
>
> On 26 July 2010 19:26, Thierry Coq wrote:
> >
> > I see units as namespaces already existing: we use the unit names to
> > prefix
> > ambiguous function or variable names for example.
>
> Unit Names give very limited namespace support - which only applies to
> types or procedures/functions or g
spir :
> Sure, but this is just a matter of convention and support by a given
> compiler:
> typeIntegers = array of Integer;
> var ints : Integers = [1,2,3];
> could work as expected by automatically sizing, allocating and
> initialising. How else could work languages that have
spir :
> Theoretically speaking, I'm all for type checking; and for programming
> discipline in general. But in practice I never get type errors.
Then you are either a genius or you are using not enough types. ;)
> So, a few questions:
> * Do you get type errors?
Occasionally, yes.
> (playing
Reimar Grabowski :
> > If you want to get better than that, you need to get system specific,
> > I'm afraid.
>
> That's not true. As Graeme already mentioned there is EpikTimer which is
> a cross-plattform, high-resolution timer (which btw works very well for
> realtime tasks).
Well, that depends
> The standard clock for the system timer runs at 1,193,182 Hz, derived
> for the original IBM PC as the 4.77 MHz processor clock divided by 4.
Digging a bit deeper clarifies it:
http://sos.enix.org/lxr/source/hwcore/i8254.c?v=6.5
|* Ahhh PC systems are nice toys: this maximum "strange" freque
> On Tue, 01 Jun 2010 19:58:54 +0200
> "Vinzent Höfler" wrote:
>
> > "spir ☣" :
> >
> > > Thank you. Using dos.getTime (including its last arg), the following
> > > returns integer time in 10^-2s units:
> > [...]
> > >
"spir ☣" :
> Thank you. Using dos.getTime (including its last arg), the following
> returns integer time in 10^-2s units:
[...]
>
> This is the needed base for my uses. (A unit of 1s is too gross for
> timing, this leads to endless runs; more precision than 10^-2s is
> unneeded.)
Actually, the r
Bee Jay :
[TDateTime]
> What if an app need a precise and correct result, say a rocket launcher?
> :D Is there other alternative solution?
Yes. Use a time type based on a fixed point representation. This eliminates
drift and accuracy issues cause by a floating point representation.
http://stop-
Bihar Anwar
> I've tried googling and searching FPC mailing list for information about
> this one, but I found nothing.
> I just found in http://www.delorie.com/djgpp/v2faq/faq3_1.html that
> DJGPP requires MS-DOS version 3.1 or later.
>
> Would someone here tell me exactly about lowest MS-D
Von: "Jürgen Hestermann"
> > it's just easier to follow the crowd
> > than fight them. :-)
>
> In the first place it is. But if it would be available, the crowd may
> change its mind.
No, she won't. She never did.
Vinzent.
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt fre
> Hello FPC-Pascal,
>
> Saturday, May 8, 2010, 4:42:46 PM, you wrote:
>
> VH> So, apart from a possibly more optimized implementation (like
> VH> not changing the allocated memory size on each single
> VH> insertion/deletion) how do you come up with the idea that adding
> VH> another layer would
> Saturday, May 8, 2010, 5:07:12 PM, you wrote:
>
> JM> And depending on the usage patterns and the size of the
> JM> elements stored in the array, it probably can be. That's all he
> JM> was saying, and only as a side remark in the context of the
> JM> discussion (which was meanly to steer away a
> 1)
> TheArray: array of ItemArray;
> AnyItem: ItemOfArray;
> [...]
> for j:=0 to 1000 do begin
>SetLength(TheArray,j+1);
>TheArray[j]:=AnyItem;
> end;
> [...]
About 1000 GetMem operations (and 1000 assignments which aren't there in the
code below, so I won't count them).
> Now h
> c> TList wraps TFPList, which is based internally on an array. So access
> c> is fast; insertion, deletion not.
>
> But it is faster than inserting elements in a dynamic array (unless
> reference counted ones) because it usually moves less amount of data
> (4/8 bytes per element).
Implementing
Bihar Anwar
> Moreover, I've seen many Delphi code snippets out there (e.g.
> http://www.cs.wisc.edu/~rkennedy/array-delete) rely on reference counting
> behaviour.
Great. I once wrote code that relied on Turbo Pascal's heap list structure
internals.
Shall I post a bug report that this doesn't
> I fear you've simply no clue about the usage,
> internals and purpose of dyn. arrays so I stop this discussion.
As you always do once someone does not share your point of view, even after you
tried so hard to convince him. :P Well, never mind.
Still, dynamic arrays are a bitch, because they on
Rainer Stratmann :
> Am Thursday 19 November 2009 23:16:26 schrieb Vinzent Höfler:
> >
> > {$HINTS OFF}
> >
> > ... code ...
> >
> > {$HINTS DEFAULT}
> >
> > maybe? Whereas DEFAULT restores the switch to the original state.
>
> But the
Martin :
> Ideally it would be, if there was a directive or similar, to suppress it
> for given lines (or statements).
> one that is easier than {$push} { $HINT OFF} ... {$POP}
{$HINTS OFF}
... code ...
{$HINTS DEFAULT}
maybe? Whereas DEFAULT restores the switch to the original state.
Vinze
Rainer Stratmann :
> For me a variable is initialised when it passes a procedure/function
> which has a var declaration in the parameters.
-- 8< --
procedure Add_2 (var I : Integer);
begin
I := I + 2;
end;
-- 8< --
If the variable for the parameter I wasn't correctly initialized before, it
Graeme Geldenhuys :
> On 19/11/2009, Jonas Maebe wrote:
> >
> > > Or is it just a side effect?
> >
> > Yes.
>
> Well it seems the "side effect" is more popular use-case in FPC and
> Delphi developers projects than the original intention of "out" then.
Of course. The side-effect is much more in
Graeme Geldenhuys :
> 2009/11/19 "Vinzent Höfler" :
> >
> > Why don't you create your own initialization routine together with the
>
> Because not all the code I maintain is my own. Some code, as in the
> case of DCPCrypt gave stacks of hints which were al
Florian Klaempfl :
> Vinzent Höfler schrieb:
> > Florian Klaempfl :
> >
> >> Out is not made to solve such problems but plainly to work with
> >> COM/Corba.
> >
> > Really? Well, that's not what the FPC manual says:
>
> And
mar...@stack.nl:
[Synapse/Synaser]
> How do you use it? I'm used to TComport, and it seems that synaser, like
> unit serial, only supports blocking use.
call Connect, call Config, call the appropriate reading and writing subroutines
(like SendString and RecvPacket)...
> Do you put it in a threa
Holger Bruns :
> > Despite queues an baud rates, you must expect data loss. You will
> > loss data in the physical layer. You have to implement some handshake
> > to prevent it. (using google translator, excuse my english).
>
> Which can be done through a direct port access and some lines of cod
Florian Klaempfl :
> Out is not made to solve such problems but plainly to work with
> COM/Corba.
Really? Well, that's not what the FPC manual says:
-- 8< --
The purpose of an out parameter is to pass values back to the calling routine:
The variable is passed by reference. The initial value of
Graeme Geldenhuys :
[FillChar]
> As for the COM usage requirement (which I honestly believe is the
> minority use case in FPC).
AFAIK, the different semantic of "out" parameters applies to all reference
counted types. That's especially unfortunate with dynamic arrays, where you
lose transparenc
Graeme Geldenhuys :
> A very quick and dirty solution would be to reimplement the public
> Create() constructor and immediately raise an exception inside it,
> explaining the problem. That way if any developer tries to use that
> default constructor, they will get an error - instead of some silent
Jonas Maebe :
> On 09 Nov 2009, at 21:03, Michael Van Canneyt wrote:
>
> > On Mon, 9 Nov 2009, "Vinzent Höfler" wrote:
> >
> >> As wrong as in "Don't call most system functions from within a
> >> signal handler.", maybe?
>
Michael Van Canneyt :
> On Mon, 9 Nov 2009, Wimpie Nortje wrote:
>
> It should stop the daemons properly. This is the code that gets executed:
>
> Procedure DoShutDown(Sig : Longint; Info : PSigInfo; Context :
> PSigContext);
> cdecl;
>
> begin
>Application.StopDaemons(True);
>Applicati
Von: Holger Bruns :
> I am rather clueless while dealing with device drivers like /dev/ttyS0
> on linux. My question is, what do I grab while reading from a device
> driver file like /dev/ttyS0?
You don't read from a "device driver". You read from a "device". What you read
is usually called "d
Von: Holger Bruns :
> If I intend
> to use device drivers, I need to know how to access the ports of a
> device, which means in my case to a serial port based on the 16550D
> Universal Asynchronous Receiver/Transmiter with FIFOs.
No.
> I need to read
> and write every register of that UART a
Holger Bruns :
> Accessing ports is limited to ports < 03ffh, more ports cannot be
> released with fpioperm. This means to me, successful serial port access
> on higher addresses cannot yet be implemented with fpc.
Or any other compiler, for that matter, because this is a system restriction.
P
Graeme Geldenhuys :
> I have been programming solely in Object Pascal for the last 9 years.
> I dab in Java every now and again (but not for any production
> software). I also read a lot of C/C++ code which I rewrite into Object
> Pascal for whatever reason. So just like me being able to read and
Graeme Geldenhuys :
> Any programmer worth hiring should find it relatively easy to switch
> to another language. Or and least become proficient in it in a
> relative short period of time. The basic principles apply to all
> languages, it's just the tool-chain and syntax that differs.
Yes and no
"Jürgen Hestermann" :
> > You can post an ad for a C
> > programmer and get 1,000 applicants, if you post an ad for a Pascal
> > programmer you might get 5, at least where I live.
Yes, and guess what: Odds are that there are more than 5 good ones out of the
1000 C-programmers than a single goo
mar...@stack.nl:
> The reason is probably more because Wirthian languages traditionally use
> recursive descent parsers.
Yeah, right.
The reason is most definitely that of all those people who know the language
well enough to write the grammar, there's no one actually doing it.
Of course, with
Graeme Geldenhuys :
> Now I know why vendors of newer languages (Dephi, Java etc) are trying
> to hide pointers from programmers. They are very tricky to work with -
> and give errors without warning!
Especially when compiler and programmer are both trying to outsmart each other.
:D
Vinzent.
-
Andrew Brunner :
> On Sun, Oct 11, 2009 at 5:25 PM, "Vinzent Höfler"
>
> Read up on forward declarations. The technique of declaring a typed
> pointer to any data structure in FPC and Delphi was that you can use
> it in fields and methods of objects and data structures
Martin :
> The beauty of the current solution is that static and dynamic arrays can
> be substituted with each other, simple by changing the declaration, and
> adding/removing a setlength. All other code can be left as it is.
No, because of subtle differences in the handling of "out" parameters
"Jürgen Hestermann" :
> Adding yet another variant is not good. I once thought that Pascal was
> superior to other languages because of it's clear and strict concept but
> now there is no longer *the* Pascal language anymore.
If you're searching for some stricter Pascal then maybe you should gi
"Jürgen Hestermann" :
> And why should that be the case? What are the outstanding feature of C
> that make it so supperiour? It's illogical and hard to maintain syntax?
Its "Compile anything, crash everywhere." interface. :P
Vinzent.
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und M
Henry Vermaak :
> You said C did it "wrong", because you think that arrays and pointers
> should be different things.
No, I said so, because arrays and pointers *are* different things (even in C
there are subtle differences - which should sort of prove my point).
Apart from that, I expect my re
mar...@stack.nl:
> > That simply means, the code is not documented. Again: Not entirely C's
> fault.
>
> Docs. Like anybody reads them.
Well, I do. If the coder cares to write any, that is. :)
Vinzent.
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer,
Andrew Brunner :
> 1st benefit:
>
> declaring methods associated with classes before TIntArray needs to be
> defined or declared.
> eg. procedure DoSomething(Var Data:TIntArray); vs (DataP:PIntArray);
Huh? Is there any difference other than the second one can take a NIL value?
> Lastly, passi
Marco van de Voort :
> And the criticism about introducing Cisms in FPC/Delphi is also old. In
> the past I would have joined you, but after a few non-trivial header
> conversions and library conversions that pretty much died out.
Yes. But that's not the fault of the C-language. That's the fault
Henry Vermaak :
> Please don't confuse your opinion with "right" and "wrong".
It's not just my opinion, that arrays and pointer are different things. One
might say it's a fact.
> Confusion and consistency were what this discussion was about.
Confusing code may have many properties. But I doubt
Henry Vermaak :
> 2009/10/10 "Vinzent Höfler" :
> > Henry Vermaak :
> >
> >> One thing I think you don't understand is that an array _is_ a
> >> pointer. Look at this table to visualise:
> >>
> >> http://en.wikipedia.org/wi
Henry Vermaak :
> Thanks for the explanation, I was under the impression that arrays in
> Pascal were similar to C. How do you explain the "automatic"
> dereferencing with a pointer to an array that Jürgen is talking about?
Those are dynamic arrays, IOW pointers disguised as arrays. This is part
mar...@stack.nl:
> In our previous episode, "Vinzent Höfler" said:
> >
> > One thing I think you don't understand is that arrays and pointers are
> > orthogonal concepts in almost every other programming language than C.
> >
> > So technicall
Henry Vermaak :
> One thing I think you don't understand is that an array _is_ a
> pointer. Look at this table to visualise:
>
> http://en.wikipedia.org/wiki/C_syntax#Accessing_elements
One thing I think you don't understand is that arrays and pointers are
orthogonal concepts in almost every o
Henry Vermaak
> I can't understand what you are trying to say. An array is a pointer
> to where the elements of the array resides in memory.
No, not in Pascal. In Pascal an array is a variable just like any other: A name
for some memory area where values can be stored.
> How else do you think
"Jürgen Hestermann" :
> >> And I don't know any other Pascal Compiler who does any checks in
> >> this direction. Do some?
> > I don't know, but ADA reportedly does.
Yes, but the semantics of discriminants is slightly different than in PASCAL.
> I don't know the differences to Pascal. Does it ha
Florian Klaempfl :
> If you have a better for unix this will be fine. IIRC it is not easy (if
> possible after all?) to implement TMultiReadExclusiveWriteSynchronizer
> for unix systems.
It's possible, yes. If it's possible in an efficient way, is another question.
Vinzent.
--
GRATIS für alle
Graeme Geldenhuys :
> I have a corrected TMultiReadExclusiveWriteSynchronizer implementation
> (don't worry, not based on Delphi implementation) that I can donate to
> FPC.
I hope it isn't based on the Delphi one. Last time I heard the Delphi
implementation suffers from occasional dead locks.
S
Graeme Geldenhuys :
> How do I convert the GetCurrentThreadID() result to a string?
>
> At the moment for Linux and Windows the following works:
>
> var
> lsThreadID: string
> begin
> lsThreadID := IntToStr(GetCurrentThreadID);
lsThreadID := SysUtils.IntToStr (QWord(GetCurrentThread
Von: "Hans Mårtensson" :
> But then, in case of zero-tolerance, if you trust the compiler, what
> about the OS? and, worst, what about your program?
And what about the CPU? ;)
> I wouldn't trust the reliability of anything before the full system has
> been tested under working conditions.
Wha
Mattias Gaertner :
> But I second Jonas mail: Before you run an fpc program in a
> zero-tolerance environment, you have to test a lot of things, because a
> lot of code was not written with zero-tolerance in mind.
Testing simply isn't enough. As we all should know, testing only proofs the
exista
> Is it possible to have a multi-threaded console application?
Yes. BTDT.
> The reason I ask, is because I can't see CheckSynchronize() being
> called anywhere in TCustomApplication descendants like what Lazarus
> (console app project) creates?
Well, if you want to do it that way, you're free to
Richard Ward writes:
> I was refering to not seeing a note that one can not
> have a unit name be the same as a function name.
Sure you can, the function just should not reside in the very same unit. This
is a short-coming of the Pascal language definition.
Vinzent.
--
Pt! Schon vom neue
Original-Nachricht
> Datum: Mon, 26 Jan 2009 17:42:23 -0600
> Von: "vmars"
> An: fpc-pascal@lists.freepascal.org
> Betreff: [fpc-pascal] If ShellExecute(0, \'open\', PChar(ExecuteName), \'\',
> \'\',0) <= 32 Then
> Thanks in advance!
>
> [Any ideas why this works:
> Ex
Original-Nachricht
> Datum: Tue, 20 Jan 2009 09:07:54 +0100 (CET)
> Von: Michael Van Canneyt
> An: FPC-Pascal users discussions
> Betreff: Re: [fpc-pascal] CPU affinity of TThread descendants
>
>
> On Mon, 19 Jan 2009, David W Noon wrote:
>
> > Hi,
> >
> > I am running FPC
Jürgen Hestermann wrote:
Mantra: First make it work, then make it fast.
In general that's true from the programmer's viewpoint. But this does
not apply to adding language details because there is no 'first make it
work'. Why obscure important implementation details if the only benefit
is sa
Jürgen Hestermann wrote:
I disagree with any statement saying that for .. in loop is
only a type-saver. It's a good language extension and should be included
(since Delphi already have this, it will also be a good idea).
Consider the
following example:
for d in [Monday,Wednesday,Friday] do ;
Michael Van Canneyt wrote:
On Wed, 31 Dec 2008, leledumbo wrote:
Since it's possible to use libc's MM via cmem unit, would the opposite be
possible?
>From the point of view of FPC, there should not be a big problem.
The C library, this is another matter. I am not sure that it
supports plug
Graeme Geldenhuys wrote:
Under linux, how do you know the users
favorite text editor?
$ echo $EDITOR
/usr/bin/vi
SCNR,
Vinzent.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
> Von: "Mattias Gärtner" <[EMAIL PROTECTED]>
> I'm curious: who needs more than 13 different image interpolations?
13 different users, of course. ;)
That was a rhetorical question, wasn't it?
Vinzent.
--
Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
http://www.gmx.
Tom Verhoeff wrote:
On Wed, Oct 29, 2008 at 09:58:10PM +0100, Vinzent Höfler wrote:
Tom Verhoeff wrote:
I am surprised that for ShortString, the range is not
also 1 <= i <= Length(s).
IIRC Turbo Pascal only allowed you to access s[0] when range checking
was off, and similarly for s[i
Tom Verhoeff wrote:
I am surprised that for ShortString, the range is not
also 1 <= i <= Length(s).
IIRC Turbo Pascal only allowed you to access s[0] when range checking
was off, and similarly for s[i] with i > Length(s).
No. See transcript:
-- 8< -- the program --
{$R+}
var
s1 : String;
Graeme Geldenhuys wrote:
Some developers prefer to pass in a GUI component to a thread
instance, so the thread knows what widget to update. Other users
prefer to post a "gui update" message to the application event queue.
I'm very new to threads and might know just enough to make in
dangerous. :
1 - 100 of 149 matches
Mail list logo
