Thread

  1. Preprocessor

    Michael Meskes <meskes@topsystem.de> — 1998-02-05T14:50:54Z

    I've just send the tar file to the patches list (hope that was correct). I'd
    like to have it included in the archive before starting more work on it.
    
    We have to decide which extension to use for embedded SQL code. Oracle
    already uses *.pc so that doesn't look good. Or shall we make it as
    compatible to Oracle as possible and use *.pc. Alternatively, how about
    *.pqc?
    
    Michael
    -- 
    Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
    meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
    meskes@debian.org                      | 52146 Wuerselen
    Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
    Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10
    
    
  2. Re: [HACKERS] Preprocessor

    Jan Wieck <jwieck@debis.com> — 1998-02-05T15:49:05Z

    > 
    > I've just send the tar file to the patches list (hope that was correct). I'd
    > like to have it included in the archive before starting more work on it.
    > 
    > We have to decide which extension to use for embedded SQL code. Oracle
    > already uses *.pc so that doesn't look good. Or shall we make it as
    > compatible to Oracle as possible and use *.pc. Alternatively, how about
    > *.pqc?
    
        *.pgc maybe
    
    > 
    > Michael
    > -- 
    > Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
    > meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
    > meskes@debian.org                      | 52146 Wuerselen
    > Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
    > Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10
    > 
    > 
    
    
    Until later, Jan
    
    -- 
    
    #======================================================================#
    # It's easier to get forgiveness for being wrong than for being right. #
    # Let's break this rule - forgive me.                                  #
    #======================================== jwieck@debis.com (Jan Wieck) #
    
    
    
  3. Re: [HACKERS] Preprocessor

    Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-02-05T16:13:52Z

    Michael Meskes wrote:
    
    > I've just send the tar file to the patches list (hope that was correct). I'd
    > like to have it included in the archive before starting more work on it.
    >
    > We have to decide which extension to use for embedded SQL code. Oracle
    > already uses *.pc so that doesn't look good. Or shall we make it as
    > compatible to Oracle as possible and use *.pc. Alternatively, how about
    > *.pqc?
    
    Ingres uses ".sc", which I imagine represented "sql c". Applix ships files for
    their database interface labeled with ".ec", which I assume represents
    "embedded c". I like the ".sc" myself, but that may be because I've worked with
    it for years :) I would think any label you choose does not need to be unique.
    What does ".pc" indicate?
    
                                                       - Tom
    
    
    
  4. Re: [HACKERS] Preprocessor

    Marc G. Fournier <scrappy@hub.org> — 1998-02-05T17:15:24Z

    On Thu, 5 Feb 1998, Thomas G. Lockhart wrote:
    
    > Michael Meskes wrote:
    > 
    > > I've just send the tar file to the patches list (hope that was correct). I'd
    > > like to have it included in the archive before starting more work on it.
    > >
    > > We have to decide which extension to use for embedded SQL code. Oracle
    > > already uses *.pc so that doesn't look good. Or shall we make it as
    > > compatible to Oracle as possible and use *.pc. Alternatively, how about
    > > *.pqc?
    > 
    > Ingres uses ".sc", which I imagine represented "sql c". Applix ships files for
    > their database interface labeled with ".ec", which I assume represents
    > "embedded c". I like the ".sc" myself, but that may be because I've worked with
    > it for years :) I would think any label you choose does not need to be unique.
    > What does ".pc" indicate?
    
    	postgresql c?
    
    
    
    
  5. Re: [HACKERS] Preprocessor

    Michael Meskes <meskes@topsystem.de> — 1998-02-06T08:42:57Z

    Thomas G. Lockhart writes:
    > Michael Meskes wrote:
    > 
    > > I've just send the tar file to the patches list (hope that was correct). I'd
    > > like to have it included in the archive before starting more work on it.
    > >
    > > We have to decide which extension to use for embedded SQL code. Oracle
    > > already uses *.pc so that doesn't look good. Or shall we make it as
    > > compatible to Oracle as possible and use *.pc. Alternatively, how about
    > > *.pqc?
    > 
    > Ingres uses ".sc", which I imagine represented "sql c". Applix ships files for
    > their database interface labeled with ".ec", which I assume represents
    > "embedded c". I like the ".sc" myself, but that may be because I've worked with
    > it for years :) I would think any label you choose does not need to be unique.
    > What does ".pc" indicate?
    
    .pc means Proc-C with proc being Oracle's preprocessor.
    
    Michael
    
    -- 
    Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
    meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
    meskes@debian.org                      | 52146 Wuerselen
    Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
    Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10