Customizing SMF > SMF Coding Discussion

Useful Applications

<< < (11/15) > >>

Warhaven:
I use the following regularly at work.  These are some (free) very useful programs that compliment Xcode very well.  Can find them all on macupdate:

TextWrangler
Programmer-friendly text editor.  Syntnax highlighting for nearly everything, as well as advanced grep find & replace.

SequelPro
Database browser.  Usual things included.

DiffMerge
File comparison.

CyberDuck and File-Zilla
FTP/SFTP clients.

SvnX
SVN tool.

Screenshots
If you didn't already know:
cmd+shift+3 (whole-screen capture)
cmd+shift+4 (selection screen capture)
cmd+shift+4, then hit space bar (allows you to click on a window, menu, dock item, icon, etc. and capture selected item)

Yoshi:
Here on Windows 7:

Text Editor: Komodo Edit
Web Server: WAMP
FTP client: FileZilla
ZIPper: WinRAR
Screenshots: Lightshot

And on Linux (Ubuntu 12.04):
Text Editor: gedit
Web Server: Custom LAMP stack
FTP client: FileZilla
ZIPper: Ubuntu stock
Screenshots: Dunno, built-in crap I guess.

I prefer the Ubuntu environment since I modified the PHP and Apache config to the way I like developing with it.

Arantor:
FWIW I do crude syntax checking by taking the string, sticking 'return true;' in front of it, then pushing it through eval() and seeing if I get true or false back.

SoLoGHoST:

--- Quote from: Arantor on September 26, 2012, 05:56:47 PM ---FWIW I do crude syntax checking by taking the string, sticking 'return true;' in front of it, then pushing it through eval() and seeing if I get true or false back.

--- End quote ---

FYI:  Not exactly the best way to check for PHP syntax errors, mainly because eval runs the PHP script/string.  It's not a syntax checking function, although it has been used as such in many ways.  The best approach you can do using eval would be to put the code in a dead code sandbox to prevent it's execution and use output buffering to catch the errors.

Arantor:
It runs the code? You don't say! Like I hadn't already accounted for that, as described, by putting return true in front of it. So that if it returns true, it's probably OK, and if returned false, it had a parse error... you know, crude like. It would be a shame if I hadn't already made that statement in the first 5 words of my post, though...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version