I understand that the PHP clippings are from
http://tedmasterweb.com/php-bbedit-clipping-set/ And, while it's certainly Complete, I'm not entirely sure it's /fast enough/. Which is to say: when I autocomplete a clipping, I end up spending more time "fixing" it to match with, say, PEAR guidelines. Take strpos, for example (split multiple lines here): int strpos ( <#string haystack#>, <#mixed needle#> <#, [int offset]#> )<#;#> To turn that into: strpos($string, 'whee'); I have to: backspace (to remove "int"), tab, $string, tab, 'whee', tab, backspace, backspace (to remove optional component and extra space before ). And, on control functions like if, it's worse, where I have to turn: if ( ) { <##> } else { <##> } into: if () { <##> } else { <##> } to match with the PEAR coding standards. Does anyone else find this to be a problem? Any desire to fix such a thing? Or, at least, write a script that "fixes" the autogenerated source to match more inline with PEAR? -- Morbus Iff ( and think about the bad things that I didn't do ) Technical: http://www.oreillynet.com/pub/au/779 Enjoy: http://www.disobey.com/ and http://www.videounderbelly.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en -~----------~----~----~----~------~----~------~--~---
