[lazarus] About compatibility???

Matjaz Mihelic matooo at email.si
Fri Mar 8 10:45:04 EST 2002




Michael Van Canneyt wrote:
Pine.WNT.4.33.0203081333260.268-100000 at malpertuus.wisa.be">
  On Sat, 9 Mar 2002, Matjaz Mihelic wrote:
  
    Mattias Gaertner wrote:
    
      On Fri, 8 Mar 2002 09:43:14 +0100 (W. Europe Standard Time)Michael Van Canneyt <michael.vancanneyt at wisa.be> wrote:
      
        
          Since it is impossible to translate any c header file to good pascal code, the current h2pas is the better solution.I would like to add a h2pas frontend to the IDE, so that using c libraries will become much easier. But before that, h2pas must be improved.
          
          What is missing in h2pas ? (except a preprocessor :) )
          
          :)If someone does that, I will write a frontend for it.
          
          What is missing?? Let's look at the thing from the right angle. I've gotsomelibrary.1.1.2. Somebody else is having somelibrary.1.1.1. This twoversions are not necesarilly compatible. But the case is the guy thatmade header translatoion had 0.3.1. Then he somehow stopedd postingupdates. We lose nobody gains.My suggestion is to go dig deep further. Combine preprocessor with gccor make this bastard, does something like that, so unit headers would beobsolete. Every got dam'n lib comes with devel. We'd gain instantlyaccess to whole api.Let's see now there will be gtk2, how long will it take to translateheaders, half of the time to gtk3, we always lose. We could do some goodthing.
          
          See my other mail for some serious obstacles to this approach.If you can solve these without changing the compiler/language,fine. If not: There is a problem :-)Personally, I think that h2pas can be extended so it tries to do abetter job, and that it should be used to create 'temporary' unitswhich are produced on the fly.The most I can agree with is to add a new keyword 'usesheader' to pascal:uses unitA; UnitB;usesheader libC1,libC2;the compiler could then try to spawn h2pas to create a temporary unitfrom the headers, which it then proceeds to compile to a real pascalunit, which is then used in further compilation.This does not compromise the pascal language, and should give allflexibility to use C libraries.As a side remark, and don't take this personal, but: please try not to useoffensive language. The use of offensive language diminishes thecredibili
ty of a message. Not just yours, but anyones message.(Unless you're posting a joke of course ;))Michael._________________________________________________________________     To unsubscribe: mail lazarus-request at miraclec.com with                "unsubscribe" as the Subject    archives at http://www.miraclec.com/list_archives/lazarus
          
Sorry about b..., it slipped me somehow and I hope nobody's feelings weren't
compromised. 'll keep my fingers on the right place by using "hammer" spell
checker not to write like that anymore.
          
I'll not write words like that anymore
I'll not write words like that anymore
I'll not write words like that anymore
I'll not write words like that anymore
I'll not write words like that anymore
'll do few hundred more but on my own computer, without using clipboard,
but this time act it was semi-joke
          
By the way I like the idea {$usesheader some.h} and using h2pas.
          
          




More information about the Lazarus mailing list