4DToday.com
4D Net Center Hosting
Home Directory Classifieds Reference Archives
Site Info
About 4DToday.com
Contact Us
Version française
Resources
4D
4D, Inc.
4D Wiki
4D Partner Central
4D Knowledgebase
4D Doc Center
Example Applications
4D BugDisplayer
4D, Inc. Training
Podcasts on 4D
Message Lists
4D Bulletin Board
4D-Forum
4D Mailing Lists
4D Tech Google Group
iNUG Archives (Nabble)
iNUG Archives (Gmane)
Other
4D Code Exchange
4D Resources
Sviluppo4D.it (Italy)
Archives
News
Last seven days
Last 30 days
Daily Tips
Last seven days
Last 30 days
Spotlights
Last seven days
Last 30 days
Surveys
Last seven days
Last 30 days
4D Summit
4D Summit 2008
4D Summit 2007
4D Summit 2005
4D Summit 2004
4D Summit 2003
4D Summit 2002
Search Archives
Daily Tips Archive
Below is a list of the tech tips in the 4DToday.com archives.
Previous Displaying 1 to 1
out of 1
Next
20/6/02 Ready to Use Compiler Stubs
Submitted by Rob Laveaux, Pluggers Software

Even if you're developing a cross-platform database, you may want to use a plug-in that's not available for both Macintosh and Windows. Since all plug-ins must be present and accounted for when you compile, you need a dummy version of the plug-in for the platform on which the plug-in isn't called. This dummy version of the plug-in is called a "stub." Often the author of the platform specific plug-in will offer a stub for the other platform, but if not, you can just make your own.

At the following URL you will find the compiler stubs I created for all platforms (Mac, Carbon and Windows):

   ftp://ftp.4dzine.com/externals/stub_plugin.sit.hqx

The main benefit of these compiler stubs is that they share a common code base and that you can safely call all the plug-in commands without getting into trouble. But all they will do is beep.

To create a compiler stub, just copy the 4BNX, 4DK#, FON#, STR#, THM# resources from the original plug-in to the resource fork of the stub plug-in.