Re: [fpc-pascal] Recursive unit/include search path
-Fu/home/me/project1/units/*.* Is there an existing recursive option like this for -Fu and -Fi? Could be useful, but dangerous if directories contain different versions of the source file in different places. Still, in many projects I get sick of continually adding new directories to the search path - and in many projects there are not more than one version of a source file kicking around. There is only simple wildcard support like: -Fu/home/fpc/packages/base/*/units/$fpctarget Recursive is too error prone and therefor not usefull ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Recursive unit search path
On 20 apr 2006, at 01:56, L wrote: -Fu/home/me/project1/units/*.* No such thing for FPC, right? Recursive units searches? Have a look at the standard /etc/fpc.cfg and you'll see things like -Fu/usr/local/lib/fpc/$fpcversion/units/$fpctarget -Fu/usr/local/lib/fpc/$fpcversion/units/$fpctarget/* So yes, it's supported (but use * and not *.* under linux/*nix, because otherwise you'll only match directory names which contain a .) Jonas ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] hot pass $LCL_PLATFORM to fpc.cfg from command line
Hi I want to pass directive from command line to fpc.cfg in fpc.cfg I have something like this -Fu/home/me/project1/units/$LCL_PLATFORM and I want to compile my program form command line fpc -dRELEASE myprogram how setup $LCL_PLATFORM Darek ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] hot pass $LCL_PLATFORM to fpc.cfg from command line
On Thu, 20 Apr 2006, darekM wrote: Hi I want to pass directive from command line to fpc.cfg in fpc.cfg I have something like this -Fu/home/me/project1/units/$LCL_PLATFORM and I want to compile my program form command line fpc -dRELEASE myprogram how setup $LCL_PLATFORM in bash: LCL_PLATFORM=gtk1 export LCL_PLATFORM in CSH: setenv LCL_PLATFORM gtk1 You should put this command in .profile (bash) or .login (csh) if you want to avoid typing it each time when you create a shell window. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Division by Zero - not raised exception
On Wednesday 19 April 2006 16:32, L505 wrote: I didn't say pure pascal programmers with no other skills. Of course you didn't say *that*. But it still sounds like you are very focused on language skills. Language skills are much less important than people usually think. most pascal programmers know databases, Assembly, and C. They also usually know at least one scripting language such as PHP. It is *not* about knowing a language (or two, or more). Knowing about stones won't give you the ability to build a house. Unfortunately most people in the software business seem to think it does. It doesn't. It's that simple. Software development is not about *where* to put this or that statement, it is much more about the *why*: In the end it's math, logic and abstraction (among some others). A particular language is just one way to express those. Of course, having some knowledge helps to get a project started, but this is too short-term thinking. I even learned by observation that having knowledge (especially about C-like languages) actually seems to hurt. And hell, I practically learned Java in a couple of days. Anything else from that point on consists in looking up the documentation on which class I may need. Well, I don't consider being able to successfully scan a telephon book for a particalur name a special skill. I just expect people to be bright enough to do *that*. Are my expectations set way too high here? I plan to hire/pay Pascal programmers at some point for future commercial projects. Who will I hire? Probably the folks that have worked with me on open source projects before. Yes, that might be a good start. But you miss the main point: that these people showed motivation and you may even be able to judge their general software-engineering abilities (how they designed their projects, modularized it, how they managed it, etc.pp). Any specific language skills are just /not/ important, believe. Of course, the willingness to do it in a different language might be. Regards, Vinzent. -- Yet a warning is nothing more than the compiler, which knows far more about the language than most of us, saying hey, you're scaring me, man. -- Jack Ganssle, Embedded Muse 129 ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Division by Zero - not raised exception
2006/4/20, Vinzent Hoefler [EMAIL PROTECTED]: On Wednesday 19 April 2006 16:32, L505 wrote: I didn't say pure pascal programmers with no other skills. Of course you didn't say *that*. But it still sounds like you are very focused on language skills. Language skills are much less important than people usually think. I totally agree that software design and abstraction of the logic concepts are vital and most important to make the difference between a good programmer/analyst and a poor one. This is a must and even if you know or not a language you will be good or not at doing amazing software and software architecture. It is like being an architect. But for the language part, I find it very important too. Maybe a little bit more that you do. I'm not fluent in English, but in French yes. I think in French, I abstract in French, I do jokes in French, I talk to people in French, I do poems and play on words in French; and I understand others doing the same thing. But in English this is not the case. I know enought to express myself with limitations. Yet, I could have amazing ideas, idioms, jokes, but be completely unable to express it or communication it in English, or in the spirit of the language. Translating a joke is almost impossible. This example being said, An architect also knowing massonery will be much better than a simple architect or a simple masson. He will understand both and be very much effective in his task. C was my first language, but I must say that Pascal is my native language in computer programming. I'm able to abstract and do pretty good software design; but when I try to put that in other languages, I'm limmited or it is impossible to apply the design with the actual langauge. So when I know i'll code in Pascal, my design will be very much improved. I already know of what I'm talking about when I design the software. I can almost see the source in my head. I know the language capabilities and limmitations. Etc. Well, it was only my point of view on the interresting point you have raised. (Still, I totally agree with you, except that language is also important. It will make the difference between two candidates with the same software design / abstraction skills and personality in the team. Best regards. -- Alexandre Leclerc ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Recursive unit/include search path
-Fu/home/fpc/packages/base/*/units/$fpctarget Recursive is too error prone and therefor not usefull thanx to all who replied, that's what I was looking for, not true recursive, just wildcards ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] x86_64-win64
People following the svn changes recently might have noticed that a lot of changes regarding win64 happened. So we're proud to announce the first x86_64-win64 snapshot which is also probably the first available OSS compiler for win64. ftp://ftpmaster.freepascal.org/pub/fpc/snapshot/v21/x86_64-win64/fpc-2.1.1.x86_64-win64.zip It is far from being ready for production use, but for first tests it should be usefull. Please note that the x86_64 win64 needs the internal linker so programs must be compiled with -Xi Awaiting your feedback and patches to improve it :) ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: x86_64-win64 [fpc-pascal]
Hello! You (Florian Klaempfl [mailto:[EMAIL PROTECTED]) wrote about [fpc-pascal] x86_64-win64 on mm/dd/ at hh:nn: FK People following the svn changes recently might have noticed that a lot of FK changes regarding win64 happened. So we're proud to announce the first FK x86_64-win64 snapshot which is also probably the first available OSS compiler FK for win64. Great! We have made our SecureBlackbox library available for compilation with FreePascal and we hope to use FreePascal for building 64-bit versions of SecureBlackbox. FK It is far from being ready for production use, but for first tests it should FK be FK usefull. What are the main issues to be aware of when building the code with this version? Sincerely yours, Eugene Mayevski ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: x86_64-win64 [fpc-pascal]
Eugene Mayevski wrote: FK It is far from being ready for production use, but for first tests it should FK be FK usefull. What are the main issues to be aware of when building the code with this version? Unknown yet, that's why this snapshot is available: to find out these issues :) ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
Congratulations! Is a new compiler define planned which distinguishes between 32 and 64 bits, irrespective of the os targeted? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
constantijnw wrote: Congratulations! Is a new compiler define planned which distinguishes between 32 and 64 bits, irrespective of the os targeted? What do you mean with this? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
Florian Klaempfl wrote:
constantijnw wrote:
Congratulations! Is a new compiler define planned which distinguishes
between 32 and 64 bits, irrespective of the os targeted?
What do you mean with this?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
To declare conditional defines like this easily:
{$ifdef cpu64}
TMyInteger = Int64;
{$else}
TMyInteger = LongInt;
{$endif}
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
constantijnw wrote:
Florian Klaempfl wrote:
constantijnw wrote:
Congratulations! Is a new compiler define planned which distinguishes
between 32 and 64 bits, irrespective of the os targeted?
What do you mean with this?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
To declare conditional defines like this easily:
{$ifdef cpu64}
TMyInteger = Int64;
{$else}
TMyInteger = LongInt;
{$endif}
http://www.freepascal.org/wiki/index.php/Writing_portable_code_regarding_the_processor_architecture#32_Bit_vs._64_Bit
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
On Thu, 20 Apr 2006, Florian Klaempfl wrote:
constantijnw wrote:
Florian Klaempfl wrote:
constantijnw wrote:
Congratulations! Is a new compiler define planned which distinguishes
between 32 and 64 bits, irrespective of the os targeted?
What do you mean with this?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
To declare conditional defines like this easily:
{$ifdef cpu64}
TMyInteger = Int64;
{$else}
TMyInteger = LongInt;
{$endif}
http://www.freepascal.org/wiki/index.php/Writing_portable_code_regarding_the_processor_architecture#32_Bit_vs._64_Bit
And of course the documentation:
http://www.freepascal.org/docs-html/prog/prog.html
more specifically:
http://www.freepascal.org/docs-html/prog/progap7.html#x291-293000G
Amazing, isn't it ;-)
Michael.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
Michael Van Canneyt wrote:
http://www.freepascal.org/wiki/index.php/Writing_portable_code_regarding_the_processor_architecture#32_Bit_vs._64_Bit
And of course the documentation:
http://www.freepascal.org/docs-html/prog/prog.html
more specifically:
http://www.freepascal.org/docs-html/prog/progap7.html#x291-293000G
Amazing, isn't it ;-)
Amazing discoveries indeed, but how do these documents relate to my
question specifically, i.e. how to fill in the mssign word:
{$ifdef ?}
TMyInteger = Int64;
{$else}
TMyInteger = LongInt;
{$endif}
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
constantijnw wrote:
Michael Van Canneyt wrote:
http://www.freepascal.org/wiki/index.php/Writing_portable_code_regarding_the_processor_architecture#32_Bit_vs._64_Bit
And of course the documentation:
http://www.freepascal.org/docs-html/prog/prog.html
more specifically:
http://www.freepascal.org/docs-html/prog/progap7.html#x291-293000G
Amazing, isn't it ;-)
Amazing discoveries indeed, but how do these documents relate to my
question specifically, i.e. how to fill in the mssign word:
There was the correct cpu64 in your previous mail :)?
{$ifdef ?}
TMyInteger = Int64;
{$else}
TMyInteger = LongInt;
{$endif}
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
Florian Klaempfl wrote:
constantijnw wrote:
Michael Van Canneyt wrote:
http://www.freepascal.org/wiki/index.php/Writing_portable_code_regarding_the_processor_architecture#32_Bit_vs._64_Bit
And of course the documentation:
http://www.freepascal.org/docs-html/prog/prog.html
more specifically:
http://www.freepascal.org/docs-html/prog/progap7.html#x291-293000G
Amazing, isn't it ;-)
Amazing discoveries indeed, but how do these documents relate to my
question specifically, i.e. how to fill in the mssign word:
There was the correct cpu64 in your previous mail :)?
{$ifdef ?}
TMyInteger = Int64;
{$else}
TMyInteger = LongInt;
{$endif}
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
So cpu64 will be the define refering to all brands of 64 bits cpu's on
all flavours of 64 bits os?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] x86_64-win64
constantijnw wrote:
Florian Klaempfl wrote:
constantijnw wrote:
Michael Van Canneyt wrote:
http://www.freepascal.org/wiki/index.php/Writing_portable_code_regarding_the_processor_architecture#32_Bit_vs._64_Bit
And of course the documentation:
http://www.freepascal.org/docs-html/prog/prog.html
more specifically:
http://www.freepascal.org/docs-html/prog/progap7.html#x291-293000G
Amazing, isn't it ;-)
Amazing discoveries indeed, but how do these documents relate to my
question specifically, i.e. how to fill in the mssign word:
There was the correct cpu64 in your previous mail :)?
{$ifdef ?}
TMyInteger = Int64;
{$else}
TMyInteger = LongInt;
{$endif}
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
So cpu64 will be the define refering to all brands of 64 bits cpu's on
all flavours of 64 bits os?
Yes. cpu64 means 64 bit pointers.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
