avoid using `eval` about declarative

[alexlawrence]

An earlier version of declarative also implemented its own option parsing in order to avoid eval(). However manual parsing has too many downsides. The above code would not work with arrays as values and definitely not with nested objects. As you mention one would also not be able to use colons inside keys and/or values.

Using an immediately invoked function object would be slightly better than eval. Though it wouldn´t be any more secure as far as I know.

[tonydspaniard]

You are right, nevertheless I modified my version to include Function and works very well.

Your library works amazingly well and already implemented to create the backbone library for php library that would use meta info for components functionality. It will be focused for Yii framework and wonder if declarative works on dynamic rendering (live events). That could be amazing. Already created php library: called wheels.
Enviado desde mi BlackBerry® de Vodafone

-----Original Message-----
From: Alex Lawrence [email protected]
Date: Mon, 10 Jun 2013 13:59:57
To: alexlawrence/[email protected]
Reply-To: alexlawrence/declarative [email protected]
Cc: Antonio [email protected]
Subject: Re: [declarative] avoid using eval (#3)

An earlier version of declarative also implemented its own option parsing in order to avoid eval(). However manual parsing has too many downsides. The above code would not work with arrays as values and definitely not with nested objects. As you mention one would also not be able to use colons inside keys and/or values.

Using an immediately invoked function object would be slightly better than eval. Though it wouldn´t be any more secure as far as I know.

---

Reply to this email directly or view it on GitHub:
#3 (comment)