[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pdt-dev] Adding support for Facebook's XHP
- From: Derek Thurn <derek@xxxxxxxx>
- Date: Wed, 11 May 2011 10:19:22 -0700
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=CD9DTGLqgEXwJ5Remsk7ScYvvNIKJU3NnRTt9M1V3EeFq/m5ozSaq6oHJF6WjAZw6k 7j0KMc2zyqjxfACdvstkW0Skm7UxfZ+BMrhMsuWvWH6wB2fCoE14hDEkG5aOq6o7+4xH kOtpTUFXaluZbfFTNe+V7OgLw/CeNYm3Aq3bE=
Fundamentally, XHP is implemented as a preprocessor for PHP, a
language extension that adds features like XML literals to PHP. The
merits of this are certainly debatable, but the fact is that it
exists. I'm open to approaching this by treating XHP as a template
type, but won't this require duplicating a lot of logic, since XHP is
99% the same as PHP?
On Wed, May 11, 2011 at 10:01 AM, Stuardo -StR- Rodríguez
> Isn't this mixing the view and the logic?
> I think it would be easier to create a view/template engine that could
> handle XHP syntax.
> IMHO, removing the constrains of PHP syntax would it make it more possible
> for the user to screw the code.
> On Wed, May 11, 2011 at 9:21 AM, Derek Thurn <derek@xxxxxxxx> wrote:
>> I'm looking in to adding support for Facebook's XHP php extensions to
>> PDT as a summer project. How difficult would this project be?
>> Basically, I'd just want to avoid throwing up a syntax error when you
>> use an XML literal in your code. Are there any extension points for
>> PDT that would be particularly suited to this task?
>> pdt-dev mailing list
> pdt-dev mailing list