|
||||||||
|
||||||||
|
||||||||
|
|
|
User Tools
2D Graphics
- Fireworks (272)
- Flash (4177)
- Gimp (257)
- Illustrator (1557)
- Paint Shop Pro (54)
- Photoshop (17352)
3D Graphics
- 3DS MAX (2468)
- AutoCAD (90)
- Blender 3d (293)
- Bryce 3d (29)
- Cinema 4D (144)
- Lightwave 3D (38)
- Maya (579)
Web Design & Development
- Adobe Flex (65)
- ASP (376)
- ASP.NET (489)
- ColdFusion (16)
- CSS (580)
- Dreamweaver (381)
- HTML (413)
- Java (768)
- Javascript (972)
- MM Fusion (1)
- MS FrontPage (20)
- Perl and CGI (128)
- PHP (1563)
- Python (69)
- Ruby on Rails (106)
- SEO (192)
- Web Design (324)
- XML (164)
Business Applications
- MS Excel (449)
- MS PowerPoint (170)
- MS Word (158)
- QuarkXPress (8)
Business Development
- Accounting (45)
- eCommerce (78)
- Legal (8)
- Marketing (245)
Databases
Desktop Programming
- C and Cpp (510)
- Delphi (21)
- Visual Basic (336)
- Visual C (29)
Video Editing
- Final Cut Studio (23)
- Premiere (64)
Miscellaneous
- P2P Filesharing (8)
- Web Hosting (160)
Newsletter
User Login
Stats
- Tutorials: 39,015
- Categories: 572
C and Cpp Tutorials : But It Worked On MY Computer...
| Portability is becoming increasingly more important nowadays with the 32-/64-bit dichotomy. Writing portable code means that something you write will compile and run on a variety of different systems with no modification to the source code. Just because it compiles doesn't mean it'll run properly. Here I will outline some common mistakes and assumptions that make code unportable, and how to avoid them. |  |
| |
|
• Discuss Tutorial
• Comment On Tutorial |
• View Tutorial
• Report Broken Link |
|
|
