Date: 05/04/01
- Next message: sniper <email protected>: "[PHP-DEV] Bug #10674 Updated: I cannot confoigure php4 with postgres sql"
- Previous message: Wez Furlong: "Re: [PHP-DEV] openssl module for php"
- In reply to: Sascha Kettler: "Re: [PHP-DEV] openssl module for php"
- Next in thread: Sascha Kettler: "Re: [PHP-DEV] openssl module for php"
- Reply: Sascha Kettler: "Re: [PHP-DEV] openssl module for php"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2001-05-04 20:21:28, "Sascha Kettler" <kettler <email protected>> wrote:
> Sounds ok, although I wouldn't call it openssl_key_* but openssl_asym_*
> similar.
Yeah, that sounds better.
> I don't know what people would prefer: Separate functions or a
> boolean. What's the general opinion on that?
IMHO, openssl_asym_public_encrypt is just a bit too long for a function
name.
I suppose a more sensible way is to define some constants (sth like):
OPENSSL_ENC_PUBLIC and OPENSSL_ENC_PRIVATE so that the parameter has an
instant obvious meaning (compared to just true/false).
Mind you: strlen(constant) + strlen(openssl_asym_encrypt) >
strlen(openssl_asym_public_encrypt)...
I suppose it's just psychological, but shorter function names seem shorter
overall (to me anyway).
--Wez.
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: sniper <email protected>: "[PHP-DEV] Bug #10674 Updated: I cannot confoigure php4 with postgres sql"
- Previous message: Wez Furlong: "Re: [PHP-DEV] openssl module for php"
- In reply to: Sascha Kettler: "Re: [PHP-DEV] openssl module for php"
- Next in thread: Sascha Kettler: "Re: [PHP-DEV] openssl module for php"
- Reply: Sascha Kettler: "Re: [PHP-DEV] openssl module for php"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

