Re: [fpc-devel] Extend the libraries people!
Florian Klaempfl wrote: Did it go through the mailing list already? I guess because it contains an attachement it is held for approval. Yes, i've already seen it in the list. Anyway, the link to the units is here http://www.bandarra.org/pascal/stringcomparison/ begin:vcard fn;quoted-printable:Andr=C3=A9 Cipriani Bandarra n;quoted-printable:Bandarra;Andr=C3=A9 Cipriani email;internet:[EMAIL PROTECTED] tel;home:(21)2527-6877 tel;cell:(21)8134-9461 x-mozilla-html:FALSE version:2.1 end:vcard ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
L505 wrote: ... But compiled with delphi compiler, or freepascal? I wonder if they have a specific restriction where you can only compile the code on their compilers... Not that I know of but.. I thought maybe you guys had come across something like that The System.pas unit is special. In older Delphi version it cannot be compiled at all, in newer versions I never tested it. The problem here are syntax errors, the implied type declarations for the standard types, and possibly the multiple use of System.pas, which is implicitly used by every unit. No intentional or expressed limitation to use an Delphi compiler, only sloppyness ;-) DoDi ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
FMTBcd implementation for FPC was Re: [fpc-devel] Extend the libraries people!
Hi are you interested in FMTBcd unit for FPC ? I would appreciate information needed for clean implementation. Page used for collecting information is: http://www.freepascal.org/wiki/index.php/BcdUnit At this moment most valuable are test cases for different functions. Also more explanation about different functions would be nice. Please don't contribute any implementation code. This is to insure that no code was copied from a copyrighted source. Thanks Jan On Jun 9, 2005, at 03:24, Florian Klaempfl wrote: Marco van de Voort wrote: On Fri, 3 Jun 2005, Kornel Kisielewicz wrote: Florian Klaempfl wrote: - write a bcd classes BCD? Binary Coded Decimal. We urgently need a bcdfmt unit as in delphi. [...] I did not find any usable info about the bcdfmt. Searching for Delphi precision tbcd on google yields: http://64.233.183.104/search?q=cache:97hnmm3AhNEJ: www.delphikingdom.com/asp/ useranswers.asp%3Fid%3D47518+tbcd+delphi+precisionhl=en which yields the type. type TBcd = packed record Precision: Byte; SignSpecialPlaces: Byte; Fraction: packed array [0..31] of Byte; end; What is the required interface for the TBCD objects? Are they normal BCD (0-9) or Telephony BCD (0-9,a-c,*,#,filler) ? (Google on TBCD took me to ASN.1) Normal I guess. A page for info about bcdfmt was started on wiki http://www.freepascal.org/wiki/index.php/BcdUnit Sorry I don't have a Delphi and I run on OS X. Do not look at delphi copyrighted source, but get info from public sources like helpfiles for download on Borlands FTP etc. This should be enough to reconstruct a rough interface, details will then later be found by testing real delphi code. The FreeCLX contains also an implementation though it's GPL while FPC libraries are modified LGPL. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
| | Another question: if someone already owns Delphi, they could compile any source code | from their Delphi CD with freepascal? Is this legal? | | Compilation for private use is legal. Borland disallows to distribute | their library source code, also in compiled (object) form unless as part | of applications. The exact license terms are part of every Delphi | distribution. But compiled with delphi compiler, or freepascal? I wonder if they have a specific restriction where you can only compile the code on their compilers... Not that I know of but.. I thought maybe you guys had come across something like that | Contributions to FPC, like to every other public project or library, | should be free from any special restrictions, so that a redistribution | can not conflict with the rights of the authors of the respective code | etc. I realize that the FPC should contain code free from restriction.. And we have to be careful with some people because some of us have copy/pasted code from the VCL and not marked it as so. I was more interested in discussing those who already have a copy of delphi and who are thinking about using freepascal.. then if say they could reuse all their delphi code in emergency, they could at least have that safety feeling in the back of their mind, when thinking about starting to use FPC. So the specific question I have is whether borland might have some restriction in the area that their source codes can only be compiled on a borland compiler... if sold commercially, or if used in freeware even. So far it seems this is not the case.. but I still don't know, there might be some little tiny wording we have missed somewhere. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
On Fri, 3 Jun 2005, Kornel Kisielewicz wrote: Florian Klaempfl wrote: - write a bcd classes BCD? Binary Coded Decimal. We urgently need a bcdfmt unit as in delphi. [...] I did not find any usable info about the bcdfmt. Searching for Delphi precision tbcd on google yields: http://64.233.183.104/search?q=cache:97hnmm3AhNEJ:www.delphikingdom.com/asp/useranswers.asp%3Fid%3D47518+tbcd+delphi+precisionhl=en which yields the type. type TBcd = packed record Precision: Byte; SignSpecialPlaces: Byte; Fraction: packed array [0..31] of Byte; end; What is the required interface for the TBCD objects? Are they normal BCD (0-9) or Telephony BCD (0-9,a-c,*,#,filler) ? (Google on TBCD took me to ASN.1) Normal I guess. A page for info about bcdfmt was started on wiki http://www.freepascal.org/wiki/index.php/BcdUnit Sorry I don't have a Delphi and I run on OS X. Do not look at delphi copyrighted source, but get info from public sources like helpfiles for download on Borlands FTP etc. This should be enough to reconstruct a rough interface, details will then later be found by testing real delphi code. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
This should be enough to reconstruct a rough interface, details will then later be found by testing real delphi code. The FreeCLX contains also an implementation though it's GPL while FPC libraries are modified LGPL. This is only interesting for Kylix licensees, and products requiring this. I'd like to keep FPC core libs free of GPL. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Well.. I had spent a lot of time thinking about how to contribute to FPC. I thought about contributing with a string phonetizer algoritm i made, but its works only for the portuguese language, so i thought i wouldnt be much usefull for most of the FPC community. Some days ago i contributed to FPC with a stringcomparator unit based on the Jaro, Winkler McLachlan and Lynch algorithms, known as the best ones to compare strings, giving them a grade between 0 and 1 (0 being no similarity between them and 1 being exactly the same). So, here goes my questions... I had no feedback for the string comparison unit so far... Was that a good contribution? Would it be a good idea to contribute with the phonetic algorithm even knowing that it works only for the portuguese language? Cheers! André Cipriani Bandarra begin:vcard fn;quoted-printable:Andr=C3=A9 Cipriani Bandarra n;quoted-printable:Bandarra;Andr=C3=A9 Cipriani email;internet:[EMAIL PROTECTED] tel;home:(21)2527-6877 tel;cell:(21)8134-9461 x-mozilla-html:FALSE version:2.1 end:vcard ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
André Cipriani Bandarra wrote: Well.. I had spent a lot of time thinking about how to contribute to FPC. I thought about contributing with a string phonetizer algoritm i made, but its works only for the portuguese language, so i thought i wouldnt be much usefull for most of the FPC community. Some days ago i contributed to FPC with a stringcomparator unit based on the Jaro, Winkler McLachlan and Lynch algorithms, known as the best ones to compare strings, giving them a grade between 0 and 1 (0 being no similarity between them and 1 being exactly the same). So, here goes my questions... I had no feedback for the string comparison unit so far... Did it go through the mailing list already? I guess because it contains an attachement it is held for approval. Was that a good contribution? Would it be a good idea to contribute with the phonetic algorithm even knowing that it works only for the portuguese language? Cheers! André Cipriani Bandarra ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
| | | Do not look at delphi copyrighted source, but get info from public sources | | like helpfiles for download on Borlands FTP etc. | | | | This should be enough to reconstruct a rough interface, details will then | | later be found by testing real delphi code. | | | | I was just wondering, are there any source code files that Borland company offers | which doesn't have copyright and is public? | Another question: if someone already owns Delphi, they could compile any source code from their Delphi CD with freepascal? Is this legal? I'm not saying that you could distribute the sources, but you could compile it with FPC? Or is that not legal? For example.. one could try compiling the Delphi VCL as a Delphi product owner, but not distribute the VCL sources themselves, just what was compiled? ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
On Thu, 9 Jun 2005, L505 wrote: | | | Do not look at delphi copyrighted source, but get info from public sources | | like helpfiles for download on Borlands FTP etc. | | | | This should be enough to reconstruct a rough interface, details will then | | later be found by testing real delphi code. | | | | I was just wondering, are there any source code files that Borland company offers | which doesn't have copyright and is public? | Another question: if someone already owns Delphi, they could compile any source code from their Delphi CD with freepascal? Is this legal? Yes. I'm not saying that you could distribute the sources, but you could compile it with FPC? Or is that not legal? It is legal, as long as you don't distribute the sources. For example.. one could try compiling the Delphi VCL as a Delphi product owner, but not distribute the VCL sources themselves, just what was compiled? This is possible, what is more, it is being done. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
On Fri, Jun 10, 2005 at 12:41:30AM +0200, Michael Van Canneyt wrote: On Thu, 9 Jun 2005, L505 wrote: | | | Do not look at delphi copyrighted source, but get info from public sources | | like helpfiles for download on Borlands FTP etc. | | | | This should be enough to reconstruct a rough interface, details will then | | later be found by testing real delphi code. | | | | I was just wondering, are there any source code files that Borland company offers | which doesn't have copyright and is public? | Another question: if someone already owns Delphi, they could compile any source code from their Delphi CD with freepascal? Is this legal? Yes. I'm not saying that you could distribute the sources, but you could compile it with FPC? Or is that not legal? It is legal, as long as you don't distribute the sources. For example.. one could try compiling the Delphi VCL as a Delphi product owner, but not distribute the VCL sources themselves, just what was compiled? This is possible, what is more, it is being done. I have several old books, with source code, covering TP6 in my library. The most interesting one to me covers generic programming; eg. arrays, lists, collections etc. These units are mainly implemented using objects and manipulating data pointers. Will any of these be of interest to the list. I will have to rework them to compile cleanly using FPC. Regards John -- Feeling exploited, impoverished or imprisoned?? Knock down the Gates of and break free into the Brave GNU World of the Free Software Foundation. Squeak with delight at pleasure this freedom brings. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
L505 wrote: | Why not both? Delphi is windows-only, so even if FPC became 100% | compatible with D7, the libraries already available for Delphi are | usually windows specific, and FPC libraries are cross-platform. And we all know they are already doing just that. What is needed is more help, action, and contribution. In fact many libraries out there already are working with FPC. We just haven't done anything about them (i.e. submitted them). It's the man work. We can talk all we want but when it comes time to code... Indeed :) ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Some of the incompatibilities first need to be brought about through experimentation. So start figuring out what -specific- delphi units that you actually need to get working now. If you have a specific unit or source code that needs to be working -today-, then at least you can submit the exact incompatibility issue to the mailing list or wherever. Otherwise, isn't the incompatibility just low priority, until proven guilty? i.e. it's great that c++ has ways to do neat tricks with all sorts of templates and preprocessing, but does any of your code that you want working today, right now, rely on it? If so, then it's a higher priority.. but if it's something you haven't used in 5-10 years and would be nice to have some day then it's just more of a wish than a need. I definitely agree that it would be nice to have all delphi code compile in FPC (then maybe Borland might sadly go out of business and we all might be eating free food soon too).. but there are other alternatives in the mean time, which may only take 5 minutes to get working. Such as getting KOL working, which is a complete GUI toolkit for windows! I thought it would take me longer to get this working today. Well I've just got a KOL application working with FPC 2.0.0, just the date/time functions and KOL assembly version define isn't working properly yet. Since Vladimir offers us pure Pascal $define or an assembly $define, I turned $define_pas mode on and got a simple KOL app working after about 1 hour of commenting out date/time functions and changing a few things. I will submit a crumby KOL hello world zip asap. (next goal is to try an MCK app working, and a linux app working, but Im not sure how far linux is supported with kol) Listen, 26KB for complete a hello world windows GUI program is not bad at all. Maybe we'll get around to making IDE for KOL/freepascal, or Lazarus could be hacked to use KOL. People might be able to cheat in the mean time by building their KOL/MCK applications inside delphi, then compiling with freepascal (since KOL does not use DFM files, rather pure on the fly component creation code just hidden inside include files). Lars | | Why not both? Delphi is windows-only, so even if FPC became 100% | | compatible with D7, the libraries already available for Delphi are | | usually windows specific, and FPC libraries are cross-platform. | | And we all know they are already doing just that. What is needed is more help, action, | and contribution. | | In fact many libraries out there already are working with FPC. We just haven't done | anything about them (i.e. submitted them). It's the man work. We can talk all we want | but when it comes time to code... | | Indeed :) | | ___ | fpc-devel maillist - fpc-devel@lists.freepascal.org | http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Some of the incompatibilities first need to be brought about through experimentation. So start figuring out what -specific- delphi units that you actually need to get working now. If you have a specific unit or source code that needs to be working -today-, then at least you can submit the exact incompatibility issue to the mailing list or wherever. I see that it would be nice to have all delphi code compile in FPC (then maybe Borland might sadly go out of business and we all might be eating free food soon too).. but there are other alternatives in the mean time, which may take less resources too. Such as getting KOL working, which is a complete GUI toolkit for windows! I thought it would take me longer to get this working today. Well I've just got a KOL application working with FPC 2.0.0. Since Vladimir offers us pure Pascal $define or an assembly $define, I turned $define pascal on and got a simple KOL app working after about 1 hour of commenting out date/time functions and changing a few things. I will submit a crumby KOL hello world zip asap. (next goal is to try an MCK app working, and a linux app working, but Im not sure how far linux is supported with kol) Listen, 26KB for complete a hello world windows GUI program is not bad at all. Where I see a big problem is lazarus not offering small EXE sizes.. since a lot of people do judge an exe by it's size. (not so much worry in GnuLinux... I don't mind shipping a 1MB linux app...since most Linux apps are usually KDE Python bloatware anyway) So until the LCL is smartlinked better or placed into a library file, I think if KOL was avail in the mean time as a temporary solution.. this would solve a lot of problems temporarily... in a quick and dirty manner (took me only 1 hour to get KOL working today...whereas LCL linked smart may take us a year). Maybe we'll get around to making IDE for KOL/freepascal, or Lazarus could be hacked to use KOL as an option. People might be able to cheat in the mean time by building their KOL/MCK applications inside delphi, then compiling with freepascal (since KOL does not use DFM files, rather pure on the fly component creation code just hidden inside include files). Lars | | Why not both? Delphi is windows-only, so even if FPC became 100% | | compatible with D7, the libraries already available for Delphi are | | usually windows specific, and FPC libraries are cross-platform. | | And we all know they are already doing just that. What is needed is more help, action, | and contribution. | | In fact many libraries out there already are working with FPC. We just haven't done | anything about them (i.e. submitted them). It's the man work. We can talk all we want | but when it comes time to code... | | Indeed :) | | ___ | fpc-devel maillist - fpc-devel@lists.freepascal.org | http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
- Original Message - From: Nikolay Nikolov [EMAIL PROTECTED] To: FPC developers' list fpc-devel@lists.freepascal.org Sent: Monday, June 06, 2005 1:16 AM Subject: Re: [fpc-devel] Extend the libraries people! | Bisma Jayadi wrote: | | Object pascal is a mature language. Some languages even adopt the concept, such | as C# or Java, with different syntaxes and styles. Do not listen to people who | said pascal is a toy language, they just don't know what they're talking about. | | Then, if we are talking about the object pascal compilers... we must admit that | Delphi/Kylix is the most popular pascal compiler. In fact, it becomes some kind | of industry standard for pascal based software engineering. | | But, now we have another pascal compiler alternative. The open source and free | one, it's FreePascal aka FPC. Since it released the v.2.0, it got more | popularity. Some people even think that it's gonna replace Delphi domination. | But, I think it's not that easy as it said. Delphi has more experiences, more | developers and community, more library supports, more products, and many more. | | If we want to make FPC as popular as Delphi and more developers interested to | use it, then we have 2 ways to do it: | | 1. Make FPC 100% compatible with latest Delphi release (I think at least D7). | Automatically, FPC will get all Delphi resources, including the codes and the | developers! There's no need to write new specific libraries for FPC. | | 2. Make FPC own environment and community. We don't need to keep up with Delphi | compatibility, make our own syntaxes and styles, build our own libraries, have | our own dignity and destiny. :) | | Which way we gonna choose? The first one? Which I think we only need to more | concentrate on the compiler development, but with ability to share the code and | community with current Delphi code and community. This will make FPC = Delphi, | or even FPC = Delphi. :) | | Or the second one? Which I think requires more works, keep up with some | selected Delphi compatibility, build our own libraries, but with freedom to | have our own special pascal. This will make FPC Delphi, or FPC Delphi, or | even FPC Delphi. | | So... which one? :) | | | Why not both? Delphi is windows-only, so even if FPC became 100% | compatible with D7, the libraries already available for Delphi are | usually windows specific, and FPC libraries are cross-platform. And we all know they are already doing just that. What is needed is more help, action, and contribution. In fact many libraries out there already are working with FPC. We just haven't done anything about them (i.e. submitted them). It's the man work. We can talk all we want but when it comes time to code... ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Why not both? Delphi is windows-only, so even if FPC became 100% compatible with D7, the libraries already available for Delphi are usually windows specific, and FPC libraries are cross-platform. I believe you know about Kylix, which is Delphi clone on linux. Delphi IDE is windows only, as Kylix IDE is linux only as well, but not the code. As long as we don't use OS specific API (windows or linux), Delphi code is cross platform (windows and linux). :) This is also applied on FPC, not all FPC libraries are cross platform, though most of them are. This is also applied on every compiler and language, except Java maybe. It depends on your code, is it targetting a specific platform or for all platforms? -Bee- has Bee.ography at: http://beeography.modblog.com ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
On Fri, 03 Jun 2005 01:26:34 -0400, you wrote: What makes python interesting are the many classes it offers by default to perform standard tasks, especially in the text treatment department; regular expression stuff etc. The same goes for most languages; Mostly it's not the language syntax that determines the productivity factor; it's the number of standard available routines. Exactly! Thanks for brining this up. If you just want more people to use Pascal, just 1) Make it simple 2) Have lots of nice tools 3) And most of all, have lots of units to do different thing Have a look at Fundamentals (http://fundementals.sourceforge.net/). It has libraries for strings, data structures, unicode, xml, etc. It's was written for Delphi, but I've gotten some way to compile under FreePascal. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Neat, I haven't come across these yet. If you -have- got some working under FPC you should upload them to contributed units section. Because if other people convert the units which have already been done by someone else, we would be doing double work ;-) Plus it gets code into a central repository this way, again so that people don't do double the work. Have a look at Fundamentals (http://fundementals.sourceforge.net/). It has libraries for strings, data structures, unicode, xml, etc. It's was written for Delphi, but I've gotten some way to compile under FreePascal. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Object pascal is a mature language. Some languages even adopt the concept, such as C# or Java, with different syntaxes and styles. Do not listen to people who said pascal is a toy language, they just don't know what they're talking about. Then, if we are talking about the object pascal compilers... we must admit that Delphi/Kylix is the most popular pascal compiler. In fact, it becomes some kind of industry standard for pascal based software engineering. But, now we have another pascal compiler alternative. The open source and free one, it's FreePascal aka FPC. Since it released the v.2.0, it got more popularity. Some people even think that it's gonna replace Delphi domination. But, I think it's not that easy as it said. Delphi has more experiences, more developers and community, more library supports, more products, and many more. If we want to make FPC as popular as Delphi and more developers interested to use it, then we have 2 ways to do it: 1. Make FPC 100% compatible with latest Delphi release (I think at least D7). Automatically, FPC will get all Delphi resources, including the codes and the developers! There's no need to write new specific libraries for FPC. 2. Make FPC own environment and community. We don't need to keep up with Delphi compatibility, make our own syntaxes and styles, build our own libraries, have our own dignity and destiny. :) Which way we gonna choose? The first one? Which I think we only need to more concentrate on the compiler development, but with ability to share the code and community with current Delphi code and community. This will make FPC = Delphi, or even FPC = Delphi. :) Or the second one? Which I think requires more works, keep up with some selected Delphi compatibility, build our own libraries, but with freedom to have our own special pascal. This will make FPC Delphi, or FPC Delphi, or even FPC Delphi. So... which one? :) -Bee- has Bee.ography at: http://beeography.modblog.com ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Angelo Bertolli wrote: What makes python interesting are the many classes it offers by default to perform standard tasks, especially in the text treatment department; regular expression stuff etc. The same goes for most languages; Mostly it's not the language syntax that determines the productivity factor; it's the number of standard available routines. Exactly! Thanks for brining this up. If you just want more people to use Pascal, just 1) Make it simple 2) Have lots of nice tools 3) And most of all, have lots of units to do different thing It's the libraries, functions, objects, etc. that really attract people. Why do you think Java got so popular? It certainly wasn't because it was lightning fast or easy to write. It was because the standard libraries that come with Java (despite Sun's insistance to try to talk about the two synonomously) were so extensive. Ever since C and its concept of including libraries, it's been obvious that this is the main attraction for people. Okay, agreed. But what is there that can be done? I mean, yes -- there are many things that can be done by Pascal guru's, but is there anything to be done by a typical Pascal programmer? (without the knowledge of similar C libraries) I'm a FreePascal programmer that would really like to contribute to the project (for all it has given me) -- but with the lack of compiler/linux related skills I don't see much I could do. -- At your service, Kornel Kisielewicz (charonATmagma-net.pl) [http://chaos.magma-net.pl/doom/] It's much easier to make an army of dumb good people than to make one single smart good guy... -- DarkGod ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Kornel Kisielewicz wrote: Angelo Bertolli wrote: What makes python interesting are the many classes it offers by default to perform standard tasks, especially in the text treatment department; regular expression stuff etc. The same goes for most languages; Mostly it's not the language syntax that determines the productivity factor; it's the number of standard available routines. Exactly! Thanks for brining this up. If you just want more people to use Pascal, just 1) Make it simple 2) Have lots of nice tools 3) And most of all, have lots of units to do different thing It's the libraries, functions, objects, etc. that really attract people. Why do you think Java got so popular? It certainly wasn't because it was lightning fast or easy to write. It was because the standard libraries that come with Java (despite Sun's insistance to try to talk about the two synonomously) were so extensive. Ever since C and its concept of including libraries, it's been obvious that this is the main attraction for people. Okay, agreed. But what is there that can be done? I mean, yes -- there are many things that can be done by Pascal guru's, but is there anything to be done by a typical Pascal programmer? (without the knowledge of similar C libraries) I'm a FreePascal programmer that would really like to contribute to the project (for all it has given me) -- but with the lack of compiler/linux related skills I don't see much I could do. - create good container classes (map, hash, trees etc.) - write a bcd classes - extend e.g. the convutils stuff - look at your own work which could be abstracted and being interesting for fpc - write docs for the already existing packages Just a few ideas :) ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Florian Klaempfl wrote: Kornel Kisielewicz wrote: Okay, agreed. But what is there that can be done? I mean, yes -- there are many things that can be done by Pascal guru's, but is there anything to be done by a typical Pascal programmer? (without the knowledge of similar C libraries) I'm a FreePascal programmer that would really like to contribute to the project (for all it has given me) -- but with the lack of compiler/linux related skills I don't see much I could do. - create good container classes (map, hash, trees etc.) That could be done... but it needs some common FPC standard -- via interfaces? Like ITreeElement, I HashElement? Anyway, I'm not good at one cycle less stuff, so such units would still need a lot of optimizing by someone else... I think I'd pass up on this one. - write a bcd classes BCD? - extend e.g. the convutils stuff Havn't seen that one yet. - look at your own work which could be abstracted and being interesting for fpc Oh my... I've got a huge library of my own things, usualy needing a lot of optimization, but mostly roguelike-games related :-/. I also have a few libraries written using Jedi-SDL. - write docs for the already existing packages This could work. But I guess the set standard for that documentation would be fpcdoc? Still need to figure out how to use that one... :-/ -- At your service, Kornel Kisielewicz (charonATmagma-net.pl) [http://chaos.magma-net.pl/doom/] ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Florian Klaempfl wrote: - write docs for the already existing packages You mean that writing a fpcdoc for the opengl headers for example would be useful for somebody? Myself, I always was uncontent with the fact that there was no opengl section in the rtl docs... -- At your service, Kornel Kisielewicz (charonATmagma-net.pl) [http://chaos.magma-net.pl] Well, the philosophy of the World of Shadows is based on most of the degenerate, immoral and foremost amoral philosophical beliefs of our world exagarated to the maximum. --Anubis ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Kornel Kisielewicz wrote: Florian Klaempfl wrote: - write docs for the already existing packages You mean that writing a fpcdoc for the opengl headers for example would be useful for somebody? Myself, I always was uncontent with the fact that there was no opengl section in the rtl docs... Well, OpenGL is only an API interface unit I'm more thinking about units containing real stuff written in FPC. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
On Fri, 3 Jun 2005, Kornel Kisielewicz wrote: Florian Klaempfl wrote: - write docs for the already existing packages You mean that writing a fpcdoc for the opengl headers for example would be useful for somebody? Myself, I always was uncontent with the fact that there was no opengl section in the rtl docs... We document only units that are written in FPC itself, not import units for system or third-party libraries. Otherwise I'd have to document the whole Win32 API, X, C library etc. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
Michael Van Canneyt wrote: On Fri, 3 Jun 2005, Kornel Kisielewicz wrote: Florian Klaempfl wrote: - write docs for the already existing packages You mean that writing a fpcdoc for the opengl headers for example would be useful for somebody? Myself, I always was uncontent with the fact that there was no opengl section in the rtl docs... We document only units that are written in FPC itself, not import units for system or third-party libraries. Otherwise I'd have to document the whole Win32 API, X, C library etc. Michael, maybe you can write a short description (wiki?) how to create documentation for units not yet documented. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Extend the libraries people!
On Fri, 3 Jun 2005, Vincent Snijders wrote: Florian Klaempfl wrote: Michael Van Canneyt wrote: On Fri, 3 Jun 2005, Kornel Kisielewicz wrote: Florian Klaempfl wrote: - write docs for the already existing packages You mean that writing a fpcdoc for the opengl headers for example would be useful for somebody? Myself, I always was uncontent with the fact that there was no opengl section in the rtl docs... We document only units that are written in FPC itself, not import units for system or third-party libraries. Otherwise I'd have to document the whole Win32 API, X, C library etc. Michael, maybe you can write a short description (wiki?) how to create documentation for units not yet documented. Maybe this page can help too: http://lazarus-ccr.sourceforge.net/kb/index.php/Lazarus_Documentation_Editor I couldn't do it better myself :-) Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
