Re: [fpc-pascal]Default calling convention
> > > > I noticed that, with FPC 1.9.4, the (default) calling convention > > "register" depends on the fact that a routine is or is not embedded > > in an other routine. > > > > With "proc(A,B,C: Longint);", if "proc" is not embedded then > > eax = A, edx = B and ecx = C but if "proc" is embedded then edx = A, > > ecx = B and C is on the stack. > > > > Is this convention definitive or temporary? I am not sure it is > > definitive since it makes the code of assembler routines dependent > > on their status: embedded or not. > > The framepointer of the parent function is passed in EAX In general it is not wise anyway to let the assembler become to dependant on calling convention. Keep on using mov eax,param1 mov ecx,param2 etc. Clearer, and doesn't have the problem between procedure/methods/nested procedures. ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal]Best PASCAL for games
> >
> > The Delphi compiler does not even support MMX, 3Dnow or any other enhanced
> > instruction sets (except through the built-in assembler). Does FPC's code
> > generator support the use of MMX, 3Dnow or other enhanced instruction sets
> > without us having to delve into assembly?
>
> No, because NMX is useless for compilers since it can't be mixed with FPU
> code. Since 1.9.2 FPC supports SSE2 for single and double float
> operations. It can be enabled using {$fputype sse2}
For {$ffutype sse2} info see also:
http://www.freepascal.org/wiki/wiki.phtml?title=Language_related_articles&PHPSESSID=761051219fe1dfed37c15a15d293a942
___
fpc-pascal maillist - [EMAIL PROTECTED]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal]Best PASCAL for games
> > > The Delphi compiler does not even support MMX, 3Dnow or any other
enhanced
> > > instruction sets (except through the built-in assembler). Does FPC's
code
> > > generator support the use of MMX, 3Dnow or other enhanced instruction
sets
> > > without us having to delve into assembly?
> >
> > No, because NMX is useless for compilers since it can't be mixed with
FPU
> > code. Since 1.9.2 FPC supports SSE2 for single and double float
> > operations. It can be enabled using {$fputype sse2}
>
> For {$ffutype sse2} info see also:
>
So theoretically, depending on the bulk of the operations, a FPC-compiled
application could be faster than a Delphi-compiled application if {$fputype
sse2} is enabled. That rocks for game development.
Sly
___
fpc-pascal maillist - [EMAIL PROTECTED]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal](no subject)
I have some big TP 5.5 program to port to some more recent compiler, and FP seems a fair choice, since a little trial convinced me of the great quality of the product. Yet my target hardware is so poor that we have to stick to MS-DOS 6.20. The fact is that I need to also port some multi-tasking software. I know DOS is not multi-tasking, but I had that software sold by a french company (that has long ago dissapeared halas) that fooled the Turbo Pascal 5.5 code into behaving in a multi tasking way (the DOS way, in fact you just switch between contexts, nothing more). I also found some interesting software on the Internet providing what I need (MTASK) yet it seems to be adapted only to the Turbo Pascal code compiled behaviour, probably much different from Free PAscal. My question is : Is there, to your knowledge, anywhere (or anyone that would know) I could get some Free Pascal code of a "multitasker" under DOS ? Regards. __ Jérémie Lefrançois 06 73 27 35 97 Consultant Altran Technologies ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal](no subject)
On Mon, 28 Jun 2004, [ISO-8859-1] Jérémie LEFRANCOIS wrote: > I have some big TP 5.5 program to port to some more recent compiler, and FP > seems a fair choice, since a little trial convinced me of the great quality of > the product. > > Yet my target hardware is so poor that we have to stick to MS-DOS 6.20. > > The fact is that I need to also port some multi-tasking software. I know DOS is > not multi-tasking, but I had that software sold by a french company (that has > long ago dissapeared halas) that fooled the Turbo Pascal 5.5 code into behaving > in a multi tasking way (the DOS way, in fact you just switch between contexts, > nothing more). > > I also found some interesting software on the Internet providing what I need > (MTASK) yet it seems to be adapted only to the Turbo Pascal code compiled > behaviour, probably much different from Free PAscal. > > My question is : > > Is there, to your knowledge, anywhere (or anyone that would know) I could get > some Free Pascal code of a "multitasker" under DOS ? This question has been asked before. See the community site: http://community.freepascal.org:1/bboard/q-and-a-fetch-msg.tcl?msg_id=GQ&topic_id=4&topic=Developing%20for%20Dos But I'm afraid the answer will turn out to be negative. Michael. ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE: [fpc-pascal](no subject)
You may have looked at this already, but can't you run win 9x of some sort eg 98. This can be quite cheap 10e or thereabouts...My guess is this'll run on a 486/pentium with 1? G disk, 16? M memory -then use dos (or even win32) fpc...This'll give you 'multitasking' of a sort and be easier to support... Regards John > -Original Message- > From: Jérémie LEFRANCOIS [mailto:[EMAIL PROTECTED] > Sent: 28 June 2004 10:46 > To: [EMAIL PROTECTED] > Subject: [fpc-pascal](no subject) > > > I have some big TP 5.5 program to port to some more recent > compiler, and FP > seems a fair choice, since a little trial convinced me of the > great quality of > the product. > > Yet my target hardware is so poor that we have to stick to > MS-DOS 6.20. > > The fact is that I need to also port some multi-tasking > software. I know DOS is > not multi-tasking, but I had that software sold by a french > company (that has > long ago dissapeared halas) that fooled the Turbo Pascal 5.5 > code into behaving > in a multi tasking way (the DOS way, in fact you just switch > between contexts, > nothing more). > > I also found some interesting software on the Internet > providing what I need > (MTASK) yet it seems to be adapted only to the Turbo Pascal > code compiled > behaviour, probably much different from Free PAscal. > > My question is : > > Is there, to your knowledge, anywhere (or anyone that would > know) I could get > some Free Pascal code of a "multitasker" under DOS ? > > Regards. > > > __ > Jérémie Lefrançois > 06 73 27 35 97 > Consultant > Altran Technologies > > ___ > fpc-pascal maillist - [EMAIL PROTECTED] > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal]RTF
--- David G Jenkins <[EMAIL PROTECTED]> wrote: > rtfpars > Contains a RTF (Rich Text Format) parsing class. All that > needs to > be done is set some event handlers and you can display RTF wherever > you > want. > > I would like to use this to generate RTF files but don't have any > documentation about the functionality of this unit. I can't help with rtfpars but I have had luck in the past using templates. RTF is pretty complicated and so constructing brand-new documents from scratch might be complex. But if you just need to create a single kind of document, perhaps with some data changed, then you can often solve the problem much more simply by: (1) create an RTF document in your favorite software; (2) Insert tags like ##ADDRESS1## where you want to substitute text; (3) read in the template and replace the tags with the text of your choice. If you have more slightly more complex needs... such as wanting to insert the text of a letter, then the RTF that marks up standard text is pretty simple, so: (1) create the RTF file; (2) break it into a "header" part and a "tail" part; (3) examine the simple mark-up for the body and write your conversion routine. This approach has some advantages: it's quick and relatively simple and it practically garuantees that the generated RTF can be read properly by your favorite software. But it can also be really cumbersome to change the template and it doesn't work if you need the fancy RTF features. There used to be a thick-ish RTF spec on the microsoft.com website that you could examine if you wanted a better understanding of RTF. -Alan ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal]RTF
> From: Alan Mead <[EMAIL PROTECTED]> > Subject:Re: [fpc-pascal]RTF > To: [EMAIL PROTECTED] > Send reply to: [EMAIL PROTECTED] > Date sent: Mon, 28 Jun 2004 09:25:19 -0700 (PDT) > --- David G Jenkins <[EMAIL PROTECTED]> wrote: > > rtfpars > > Contains a RTF (Rich Text Format) parsing class. All that > > needs to > > be done is set some event handlers and you can display RTF wherever > > you > > want. > > > > I would like to use this to generate RTF files but don't have any > > documentation about the functionality of this unit. > > I can't help with rtfpars but I have had luck in the past using > templates. RTF is pretty complicated and so constructing brand-new > documents from scratch might be complex. But if you just need to > create a single kind of document, perhaps with some data changed, > then you can often solve the problem much more simply by: (1) create > an RTF document in your favorite software; (2) Insert tags like > ##ADDRESS1## where you want to substitute text; (3) read in the > template and replace the tags with the text of your choice. > > If you have more slightly more complex needs... such as wanting to > insert the text of a letter, then the RTF that marks up standard text > is pretty simple, so: (1) create the RTF file; (2) break it into a > "header" part and a "tail" part; (3) examine the simple mark-up for > the body and write your conversion routine. > > This approach has some advantages: it's quick and relatively simple > and it practically garuantees that the generated RTF can be read > properly by your favorite software. But it can also be really > cumbersome to change the template and it doesn't work if you need the > fancy RTF features. > > There used to be a thick-ish RTF spec on the microsoft.com website > that you could examine if you wanted a better understanding of RTF. > > -Alan > > ___ > fpc-pascal maillist - [EMAIL PROTECTED] > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > And if you only are able to to so, abandon RTF and turn into fully transparent an more flexible XML. Thre is a serious chance that your-data --(your-app)--> xml --(standard xsl)--> rtf scenario would be easier to handle. With regards, Jan Jelowicki [EMAIL PROTECTED] --- Wroclaw University of AgricultureAkademia Rolnicza we Wroclawiu Department of MathematicsKatedra Matematyki --- ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE: [fpc-pascal](no subject)
Lee, John said: > You may have looked at this already, but can't you run win 9x of some > sort eg 98. This can be quite cheap 10e or thereabouts...My guess is > this'll run on a 486/pentium with 1? G disk, 16? M memory -then use dos > (or even win32) fpc... I'd add to this - what's your (the original poster) definition of “weak hardware”, and what is the program intended to do (at least roughly - what kind of tasks)? This might help to find the best alternative solution if necessary. Regards Tomas ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal]64 bit
The website says that "The first 64-bit port has arrived. Tonight, FPC compiled itself for the first time on a 64-bit system. The system was of the AMD64 type." However I can't find any more information. Do I just download and compile the source it in the normal way? I have a dual opteron with SuSe 9.1 - Richard. -- Richard Kimber http://www.psr.keele.ac.uk/ ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal]64 bit
> The website says that > > "The first 64-bit port has arrived. Tonight, FPC compiled itself for the > first time on a 64-bit system. The system was of the AMD64 type." > > However I can't find any more information. Do I just download > and compile the source it in the normal way? No, one really needs to treat it as a separate architecture. So crosscompiling with cross-binutils. ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal]RTF
>But if you just need to create a single kind of document,
>perhaps with some data changed, then you can often solve the
>problem much more simply by: (1) create an RTF document in
>your favorite software; (2) Insert tags like ##ADDRESS1## where
>you want to substitute text; (3) read in the template and
>replace the tags with the text of your choice.
I recently wrote a program that does this. My primary problem
arose from microsoft word being stupid (big surprise, huh?)
Suppose I inserted a tag such as the above example, ##ADDRESS1##
(I think I used greater-than/less-than brackets rather than
pound symbols -- but those don't email well!) MS Word would
sometimes insert rtf tags right in the middle of the word, for
no obvious reason. So I would get something like:
##ADDR{\bizarre rtf tag, sometimes
containing carriage returns in the middle} ESS1##
My solution was to save as Word version 2, close and reopen,
then save as rtf. It might not be a bad idea to go with the XML
or LaTeX. But if you'd like a copy of the program I wrote, let
me know and I'll post it or email it to you.
~David
___
fpc-pascal maillist - [EMAIL PROTECTED]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
