DelphiWorks
delphiworks is a collection of 16 Units, 308 procedures and functions, 98 records/types and 121 constants. A complete documentation is available as compiled HTML help file ( CHM ), as a HTML offline pack or online at authors website ( http://delphiworks.sourceforge.net ). All help files available in german language! Tools for: date/time conversions, registry, multimonitor systems, files and drives, HTML, INI-files, MP3, networks, Windows NT special funtions, numerics and mathematics, operating systems, printers, string- conversions, system internal functions and many many more!
KI-Zusammenfassung: This codebase represents a historical implementation of the logic described in the metadata. Our preservation engine analyzes the structure to provide context for modern developers.
Upload <font face="Verdana" size="2"> <b>An Important Note About .inc Files</b> <p>This is just a quick note about using include files with the ".inc" file extension. This doesn't apply to <b>JUST</b> PHP, but the web in general. I am posting this here in the PHP section because that is the server side language that I use, and I have noticed an abundance of ".inc" files in various projects throughout PSC.</p> <p>For those who don't know, ".inc" files are nothing more than a file that generally contains information that you would need to access from various scripts on a site. Most often, they are a time saving way of storing certain variables. A primary example is Login/Passwords for database connections. This way, if you change the login/pass for the database, you only need to update one file.</p> <p>The problem is, however, that the contents of ".inc" can be viewed in a browser by simply typing in the path. So anyone who knew the path of your include file could easily find out information that you probably didn't want them to know. Now, to those who aren't all that concerned with security, this may not seem a big issue. However, for the more paranoid among us, it is an issue.</p> <p>I'm not sure if this applies to all platforms. The server I use runs Apache on Slackware, and the SysOp is a pretty security conscious person. Also, it could vary well be just an IE6 thing, as I have not had a chance to test this in any other browser. However, I thought I would make the uninformed among you aware of this.</p> <p>The best way to get around this is to simply change the file extension to ".php" (or whatever language your using). It's that easy. Don't let your information be compromised.</p> </font>