Code/Resource
Windows Develop
Linux-Unix program
Internet-Socket-Network
Web Server
Browser Client
Ftp Server
Ftp Client
Browser Plugins
Proxy Server
Email Server
Email Client
WEB Mail
Firewall-Security
Telnet Server
Telnet Client
ICQ-IM-Chat
Search Engine
Sniffer Package capture
Remote Control
xml-soap-webservice
P2P
WEB(ASP,PHP,...)
TCP/IP Stack
SNMP
Grid Computing
SilverLight
DNS
Cluster Service
Network Security
Communication-Mobile
Game Program
Editor
Multimedia program
Graph program
Compiler program
Compress-Decompress algrithms
Crypt_Decrypt algrithms
Mathimatics-Numerical algorithms
MultiLanguage
Disk/Storage
Java Develop
assembly language
Applications
Other systems
Database system
Embeded-SCM Develop
FlashMX/Flex
source in ebook
Delphi VCL
OS Develop
MiddleWare
MPI
MacOS develop
LabView
ELanguage
Software/Tools
E-Books
Artical/Document
env-vc.lnt
Package: pc-lint.v8.00e.zip [view]
Upload User: tt5168365
Upload Date: 2019-04-19
Package Size: 3137k
Code Size: 2k
Category:
Exploit
Development Platform:
C/C++
- /*
- env-vc.lnt: environment parameters for Microsoft's Visual C++ WorkBench
- If you are using the Microsoft Visual Workbench and you wish to invoke
- PC-lint from that environment then do the following.
- Consult the appropriate Microsoft documentation in the "Visual
- Workbench User's Guide", Chapter "Customizing Visual Workbench".
- From the Options Menu, Select the Tools command and Select "Add"
- First select the PC-lint directory (say C:LINTPP)
- and then select the file to be run, presumably LINT.EXE.
- Provide the following information (or some suitable variation):
- Command Line C:LINTPPLINT.EXE
- Menu Text PC-lint (unit check)
- Arguments -iC:LINTPP -u std.lnt env-vc.lnt $FileName
- Initial Directory $FileDir
- This will result in the Tools menu containing the additional item
- "PC-lint (unit check)".
- Note that by providing an "Initial Directory" and a local "$FileName"
- the containing directory can have a std.lnt that overrides the
- global std.lnt. Also file-names in messages are not so long.
- You will probably want to heed the following advice from the
- Microsoft documentation: "To keep an MS-DOS window open with the
- output of a command-line tool after the tool has been run
- from the Tools menu, use the Windows PIF Editor to edit the
- file _DEFAULT.PIF and clear the Close Window on Exit check box."
- Also PC-lint can be run as a windowed application so you may
- want to check that box too.
- */