Re: plPHP -- sort of an announcement.. but not commercial - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: plPHP -- sort of an announcement.. but not commercial
Date
Msg-id 3F2EC0B2.5090906@commandprompt.com
Whole thread Raw
In response to Re: plPHP -- sort of an announcement.. but not commercial  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: plPHP -- sort of an announcement.. but not commercial  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
>
> Do we need official permission to call the language plPHP by the way?
> That's the only part of the PHP license I'm wondering about.


 From what I read:

Products derived from this software may not be called "PHP", nor
      may "PHP" appear in their name, without prior written permission
      from group@php.net.  You may indicate that your software works in
      conjunction with PHP by saying "Foo for PHP" instead of calling
      it "PHP Foo" or "phpfoo"


No. We don't need to do that. We couldn't call it PHP Procedural
Language but Procedural Language for PHP (plPHP) is ok.

Sincerely,

Joshua Drake



pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: plPHP -- sort of an announcement.. but not commercial
Next
From: Richard Welty
Date:
Subject: varchar, text and cidr