8 | 9 |
-
10 |
11 |
-
13 |
14 | double 15 | _aligner; 16 | 17 | -
18 |
19 | on a Sparc, the int below wasn't enough...
20 |
21 | 22 |23 | 24 | 25 |
26 | - 27 |
28 | t4_byte* 29 | _contents; 30 | 31 |- 32 | 33 | 34 | 35 |
36 | 37 | 38 |
- 27 |
41 | class 42 | c4_Bytes::NONAME 43 | 44 | 45 | 46 | -------------------------------------------------------------------------------- /demos/struct.cpp: -------------------------------------------------------------------------------- 1 | // This command-line utility displays the data structure of a datafile 2 | // created with the Metakit library as a one-line description. 3 | 4 | #include "mk4.h" 5 | 6 | #include
8 | 9 |
-
10 |
11 |
-
13 |
14 | virtual int 15 | Read (void* buffer_, int length_); 16 | 17 | -
18 |
19 |
20 | Fetch some bytes sequentially
21 |
22 | 23 | 24 |
25 | - 26 |
27 | virtual void 28 | Write (const void* buffer_, int length_); 29 | 30 |- 31 | 32 | 33 | Store some bytes sequentially 34 |
35 | 36 | 37 |
38 | - 39 |
40 | virtual 41 | ~c4_Stream (); 42 | 43 |- 44 | 45 | 46 | 47 |
48 | 49 | 50 |
- 26 |
53 | class 54 | c4_Stream 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /python/PyStorage.h: -------------------------------------------------------------------------------- 1 | // PyStorage.h -- 2 | // $Id$ 3 | // This is part of MetaKit, see http://www.equi4.com/metakit.html 4 | // Copyright (C) 1999-2004 Gordon McMillan and Jean-Claude Wippler. 5 | // 6 | // Storage class header 7 | 8 | #if !defined INCLUDE_PYSTORAGE_H 9 | #define INCLUDE_PYSTORAGE_H 10 | 11 | #include
-
5 |
6 | class c4_Bytes::NONAME
7 |
8 | 9 | - 10 | 11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | t4_byte* 26 | | 27 |
28 | |
34 |
| 38 | double 39 | | 40 |
41 | |
47 |
57 | 58 |
| 61 | Header file 62 | | 63 |64 | "mk4.h" -- Dec 9, 1999 65 | | 66 |
9 | Metakit sample code - MkOptim
10 | 11 |
This a generic utility for the Metakit library.
12 | 13 |What it does: MkOptim is a utility program which copies data from 14 | one Metakit file to another. This has the effect of optimizing the datafile 15 | (automatic integer sizing and compaction to remove all unused space) and of 16 | converting old datafile formats to the current one.
17 | 18 |What it illustrates: ***TBD***
19 | 20 |How to use it: ***TBD***. 21 |
22 | 23 |Known problems: None.
24 | 25 |Files in EXAMPLES\MKOPTIM:
26 | 27 |MKOPTIM.CPP - MkOptim main program
28 |
MKOPTIM.MAK, MKOPTIM.DSP - MSVC 5.0 project makefiles for Win32
32 | || 33 | Roadmap 34 | Class Index 35 | Sample Index 36 | || 37 | Introduction 38 | Tips and Tricks 39 | || 40 | 41 |
9 | Metakit sample code - Dbf2mk
10 | 11 |
This is a generic utility for the Metakit library.
12 | 13 |What it does: Dbf2mk is a utility program which reads data from one 14 | or more industry-standard DBF files and saves the data in a Metakit datafile.
15 | 16 |What it illustrates: ***TBD***
17 | 18 |How to use it: ***TBD***. 19 |
20 | 21 |Known problems: None. This utility has not yet been extensively 22 | tested. This version can handle files of any size, but it does not load 23 | DBase "memo" fields and ignores all index files and calculated fields.
24 | 25 |Files in EXAMPLES\DBF2MK:
26 | 27 |DBF2MK.CPP - Dbf2mk main program
28 |
DBF2MK.MAK, DBF2MK.DSP - MSVC 5.0 project makefiles for Win32
32 | || 33 | Roadmap 34 | Class Index 35 | Sample Index 36 | || 37 | Introduction 38 | Tips and Tricks 39 | || 40 | 41 |
-
5 |
6 | class c4_Stream
7 |
8 | 9 | -
10 | A stream is a virtual helper class to serialize in binary form.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | virtual 26 | | 27 |
28 | |
34 |
| 38 | virtual int 39 | | 40 |
41 | 46 | Fetch some bytes sequentially 47 | |
48 |
| 52 | virtual void 53 | | 54 |
55 | 60 | Store some bytes sequentially 61 | |
62 |
72 | 73 |
| 76 | Header file 77 | | 78 |79 | "mk4.h" -- Dec 9, 1999 80 | | 81 |
9 | Metakit sample code - Demo
10 | 11 |
This example is more a "proof of concept" than anything else...
12 | 13 |What it does: Demo creates a simple view on disk, makes a few 14 | changes to the data as well as the structure, and then saves these too. 15 |
16 | 17 |What it illustrates: This sample program shows how to set up 18 | a simple program which uses Metakit. The source code of this 19 | application can be compiled for 32-bit Windows (as console application) 20 | as well as for 16-bit small-model DOS targets. When run more than once, i.e. with an existing 21 | datafile, this program will cause some changes to the data which illustrate 22 | the effects of "on-the-fly data restrcuturing". 23 | Demo has little practical use, other than to show you 24 | how to get started with Metakit.
25 | 26 |How to use it: When you launch the 16-bit DOS version called DEMO16.EXE, 27 | it creates a datafile called "myfile.dat", saves some 28 | data to it, and then reopens it and displays the line: 29 |
The country of Paco Pena is: Spain30 | 31 | By following the code, you can see where this came from. You can use the Metakit 32 | dump utility (see below) to examine the contents of the data file. 33 | 34 |
Known problems: None.
35 | 36 |Files in EXAMPLES\DEMO:
37 | 38 |DEMO.CPP - Demo main program
39 |
DEMO.MAK, DEMO.MDP - MSVC 4.2 project makefiles for Win32
40 |
DEMO16.MAK - MSVC 1.52 project makefile
41 |
42 |
43 |
44 | || 45 | Roadmap 46 | Class Index 47 | Sample Index 48 | || 49 | Introduction 50 | Tips and Tricks 51 | || 52 | 53 |
-
5 |
6 | class c4_IntRef
7 | : public c4_Reference
8 | 9 | -
10 | Used to get or set integer values.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | 26 | | 27 |
28 | 33 | Constructor 34 | |
35 |
| 39 | operator 40 | | 41 |
42 | 47 | Get the value as long integer 48 | |
49 |
| 53 | c4_IntRef& 54 | | 55 |
56 | 61 | Set the value to the specified long integer 62 | |
63 |
73 | 74 |
| 77 | Header file 78 | | 79 |80 | "mk4.h" -- Dec 9, 1999 81 | | 82 |
| 89 | Derived from 90 | | 91 |92 | 93 | c4_Reference 94 | 95 | | 96 |
-
5 |
6 | class c4_StringRef
7 | : public c4_Reference
8 | 9 | -
10 | Used to get or set string values.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | 26 | | 27 |
28 | 33 | Constructor 34 | |
35 |
| 39 | operator const 40 | | 41 |
42 | 47 | Get the value as string 48 | |
49 |
| 53 | c4_StringRef& 54 | | 55 |
56 | 61 | Set the value to the specified string 62 | |
63 |
73 | 74 |
| 77 | Header file 78 | | 79 |80 | "mk4.h" -- Dec 9, 1999 81 | | 82 |
| 89 | Derived from 90 | | 91 |92 | 93 | c4_Reference 94 | 95 | | 96 |
-
5 |
6 | class c4_FloatRef
7 | : public c4_Reference
8 | 9 | -
10 | Used to get or set floating point values.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | 26 | | 27 |
28 | 33 | Constructor 34 | |
35 |
| 39 | operator 40 | | 41 |
42 | 47 | Get the value as floating point 48 | |
49 |
| 53 | c4_FloatRef& 54 | | 55 |
56 | 61 | Set the value to the specified floating point 62 | |
63 |
73 | 74 |
| 77 | Header file 78 | | 79 |80 | "mk4.h" -- Dec 9, 1999 81 | | 82 |
| 89 | Derived from 90 | | 91 |92 | 93 | c4_Reference 94 | 95 | | 96 |
-
5 |
6 | class c4_DoubleRef
7 | : public c4_Reference
8 | 9 | -
10 | Used to get or set double precision values.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | 26 | | 27 |
28 | 33 | Constructor 34 | |
35 |
| 39 | operator 40 | | 41 |
42 | 47 | Get the value as floating point 48 | |
49 |
| 53 | c4_DoubleRef& 54 | | 55 |
56 | 61 | Set the value to the specified floating point 62 | |
63 |
73 | 74 |
| 77 | Header file 78 | | 79 |80 | "mk4.h" -- Dec 9, 1999 81 | | 82 |
| 89 | Derived from 90 | | 91 |92 | 93 | c4_Reference 94 | 95 | | 96 |
-
5 |
6 | class c4_ViewRef
7 | : public c4_Reference
8 | 9 | -
10 | Used to get or set view values.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | 26 | | 27 |
28 | 33 | Constructor 34 | |
35 |
| 39 | operator 40 | | 41 |
42 | 47 | Get the value as view 48 | |
49 |
| 53 | c4_ViewRef& 54 | | 55 |
56 | 61 | Set the value to the specified view 62 | |
63 |
73 | 74 |
| 77 | Header file 78 | | 79 |80 | "mk4.h" -- Dec 9, 1999 81 | | 82 |
| 89 | Derived from 90 | | 91 |92 | 93 | c4_Reference 94 | 95 | | 96 |
9 | Metakit sample code - MyIO
10 | 11 |
This example demonstrates how to setup low-level datafile encryption with Metakit.
12 | 13 |What it does: MyIO creates a simple view on disk, and then loads it back in. 14 | The data on disk is stored in a simple encrypted format. 15 |
16 | 17 |What it illustrates: This sample program shows how to customize Metakit 18 | via its "Strategy" object.
Just to show it can be done, MyIO also disables all 19 | flush calls issued by Metakit. This slightly reduces the fail-safe properties but 20 | improves performance with frequent commits on systems which implement caching using 21 | "lazy writes" (such as Windows).
The source code of this 22 | application can be compiled for 32-bit Windows (as console application) 23 | as well as for 16-bit DOS targets. MyIO has no practical use, but it contains a 24 | "CEncryptStrategy" class which you can adapt to suit your purposes.
25 | 26 |How to use it: When you launch MYIO.EXE, it creates a datafile called "secret.dat", 27 | saves some string data to it, then reads that back and displays these strings. 28 |
Note that due to the encrypted 29 | storage format you can NOT use the Metakit dump utility to examine the contents of the data file. 30 | You can of course build your own version of it, since all the necessary source code is included. 31 | 32 |
Known problems: None.
33 | 34 |Files in EXAMPLES\MYIO:
35 | 36 |MYIO.CPP - MyIO main program
37 |
MYIO.MAK, MYIO.MDP - MSVC 4.2 project makefiles for Win32
38 |
MYIO16.MAK - MSVC 1.52 project makefile
39 |
40 |
41 |
42 | || 43 | Roadmap 44 | Class Index 45 | Sample Index 46 | || 47 | Introduction 48 | Tips and Tricks 49 | || 50 | 51 |
-
5 |
6 | class c4_BytesRef
7 | : public c4_Reference
8 | 9 | -
10 | Used to get or set binary object values.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | 26 | | 27 |
28 | 33 | Constructor 34 | |
35 |
| 39 | operator 40 | | 41 |
42 | 47 | Get the value as binary object 48 | |
49 |
| 53 | c4_BytesRef& 54 | | 55 |
56 | 61 | Set the value to the specified binary object 62 | |
63 |
73 | 74 |
| 77 | Header file 78 | | 79 |80 | "mk4.h" -- Dec 9, 1999 81 | | 82 |
| 89 | Derived from 90 | | 91 |92 | 93 | c4_Reference 94 | 95 | | 96 |
Class Index 9 |
Sample Index 10 |
Tips and Tricks 11 |
14 | 15 | 16 | 17 |
c4_Bytes 18 | 19 |
c4_BytesProp 20 | 21 |
c4_BytesRef 22 | 23 |
c4_Cursor 24 | 25 |
c4_CustomViewer 26 | 27 |
c4_DoubleProp 28 | 29 |
c4_DoubleRef 30 | 31 |
c4_FloatProp 32 | 33 |
c4_FloatRef 34 | 35 |
c4_IntProp 36 | 37 |
c4_IntRef 38 | 39 |
c4_MemoProp 40 | 41 |
c4_MemoRef 42 | 43 |
c4_Property 44 | 45 |
c4_Reference 46 | 47 |
c4_Row 48 | 49 |
c4_RowRef 50 | 51 |
c4_Sequence 52 | 53 |
c4_Storage 54 | 55 |
c4_Strategy 56 | 57 |
c4_Stream 58 | 59 |
c4_StringProp 60 | 61 |
c4_StringRef 62 | 63 |
c4_View 64 | 65 |
c4_ViewProp 66 | 67 |
c4_ViewRef 68 | 69 | 70 | 71 | 72 | -------------------------------------------------------------------------------- /win/msvc60/mkdist.dsp: -------------------------------------------------------------------------------- 1 | # Microsoft Developer Studio Project File - Name="mkdist" - Package Owner=<4> 2 | # Microsoft Developer Studio Generated Build File, Format Version 6.00 3 | # ** DO NOT EDIT ** 4 | 5 | # TARGTYPE "Win32 (x86) Console Application" 0x0103 6 | 7 | CFG=mkdist - Win32 Release 8 | !MESSAGE This is not a valid makefile. To build this project using NMAKE, 9 | !MESSAGE use the Export Makefile command and run 10 | !MESSAGE 11 | !MESSAGE NMAKE /f "mkdist.mak". 12 | !MESSAGE 13 | !MESSAGE You can specify a configuration when running NMAKE 14 | !MESSAGE by defining the macro CFG on the command line. For example: 15 | !MESSAGE 16 | !MESSAGE NMAKE /f "mkdist.mak" CFG="mkdist - Win32 Release" 17 | !MESSAGE 18 | !MESSAGE Possible choices for configuration are: 19 | !MESSAGE 20 | !MESSAGE "mkdist - Win32 Release" (based on "Win32 (x86) Console Application") 21 | !MESSAGE 22 | 23 | # Begin Project 24 | # PROP AllowPerConfigDependencies 0 25 | # PROP Scc_ProjName "" 26 | # PROP Scc_LocalPath "" 27 | CPP=cl.exe 28 | RSC=rc.exe 29 | # PROP BASE Use_MFC 0 30 | # PROP BASE Use_Debug_Libraries 0 31 | # PROP BASE Output_Dir "Release" 32 | # PROP BASE Intermediate_Dir "Release" 33 | # PROP BASE Target_Dir "" 34 | # PROP Use_MFC 0 35 | # PROP Use_Debug_Libraries 0 36 | # PROP Output_Dir "..\..\builds\msvc60\mkdist\Release" 37 | # PROP Intermediate_Dir "..\..\builds\msvc60\mkdist\Release" 38 | # PROP Ignore_Export_Lib 0 39 | # PROP Target_Dir "" 40 | # ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c 41 | # ADD CPP /nologo /MD /W3 /GX /O2 /Ob2 /I "..\..\include" /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /FD /c 42 | # SUBTRACT CPP /YX 43 | # ADD BASE RSC /l 0x409 /d "NDEBUG" 44 | # ADD RSC /l 0x409 /d "NDEBUG" 45 | BSC32=bscmake.exe 46 | # ADD BASE BSC32 /nologo 47 | # ADD BSC32 /nologo 48 | LINK32=link.exe 49 | # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /machine:I386 50 | # ADD LINK32 /nologo /subsystem:console /machine:I386 /out:"..\..\builds\mkdist.exe" 51 | # Begin Target 52 | 53 | # Name "mkdist - Win32 Release" 54 | # Begin Source File 55 | 56 | SOURCE=..\..\demos\demo.cpp 57 | # End Source File 58 | # End Target 59 | # End Project 60 | -------------------------------------------------------------------------------- /python/PyProperty.cpp: -------------------------------------------------------------------------------- 1 | // PyProperty.cpp -- 2 | // $Id$ 3 | // This is part of MetaKit, the homepage is http://www.equi4.com/metakit.html 4 | // Copyright (C) 1999-2004 Gordon McMillan and Jean-Claude Wippler. 5 | // 6 | // Property class implementation 7 | 8 | #include "PyProperty.h" 9 | #include
10 | 11 | Internally, row references are very similar to cursors, in fact they are 12 | little more than a wrapper around them. The essential difference is one 13 | of semantics: comparing row references compares contents, copying row 14 | references copies the contents, whereas cursor comparison and copying 15 | deals with the pointer to the row, not its contents. 16 | 17 |
18 | 19 | 20 | 21 |
22 | 23 |
-
24 |
25 |
-
27 |
28 | c4_View 29 | Container () const; 30 | 31 | -
32 |
33 |
34 | Return the underlying container view
35 |
36 | 37 | 38 |
39 | - 40 |
41 | c4_Cursor 42 | _cursor; 43 | 44 |- 45 | 46 | 47 | 48 |
49 | 50 | 51 |
52 | - 53 |
54 | 55 | c4_RowRef (c4_Cursor); 56 | 57 |- 58 | 59 | 60 | Constructor, not for general use 61 |
62 | 63 | 64 |
65 | - 66 |
67 | c4_Cursor 68 | operator& () const; 69 | 70 |- 71 | 72 | 73 | Return the cursor associated to this row 74 |
75 | 76 | 77 |
78 | - 79 |
80 | c4_RowRef 81 | operator= (const c4_RowRef& row_); 82 | 83 |- 84 | 85 | 86 | Assign the value of another row to this one 87 |
88 | 89 | 90 |
- 40 |
93 | class 94 | c4_RowRef 95 | 96 | 97 | 98 | -------------------------------------------------------------------------------- /doc/api/c4_CustomViewer_desc.html: -------------------------------------------------------------------------------- 1 |
-
5 |
6 | class c4_CustomViewer
7 |
8 | 9 | -
10 | Abstract base class for definition of custom views.
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | virtual 26 | | 27 |
28 | 33 | Destructor 34 | |
35 |
| 39 | virtual c4_View 40 | | 41 |
42 | 47 | Return the structure of this view (initialization, called once) 48 | |
49 |
| 53 | virtual int 54 | | 55 |
56 | 61 | Return the number of rows in this view 62 | |
63 |
| 67 | virtual bool 68 | | 69 |
70 | 75 | Fetch one data item, return it as a generic data value 76 | |
77 |
| 86 | Protected members 87 | | 88 ||
| 92 | 93 | | 94 |
95 | Constructor, must be overriden in derived class 98 | |
99 |
107 | 108 |
| 111 | Header file 112 | | 113 |114 | "mk4.h" -- Dec 9, 1999 115 | | 116 |
11 | 12 | Custom views are read-only in this version, and cannot propagate changes. 13 |
14 | 15 | To implement a custom view, you must derive your viewer from this base 16 | class and define each of the virtual members. Then create a new object 17 | of this type on the heap and pass it to the c4_View constructor. Your 18 | viewer will automatically be destroyed when the last reference to its 19 | view goes away. See the DBF2MK sample code for an example of a viewer. 20 | 21 |
22 | 23 | 24 | 25 |
26 | 27 |
-
28 |
29 |
-
31 |
32 | virtual bool 33 | GetItem (int row_, int col_, c4_Bytes& buf_); 34 | 35 | -
36 |
37 |
38 | Fetch one data item, return it as a generic data value
39 |
40 | 41 | 42 |
43 | - 44 |
45 | virtual int 46 | GetSize (); 47 | 48 |- 49 | 50 | 51 | Return the number of rows in this view 52 |
53 | 54 | 55 |
56 | - 57 |
58 | virtual c4_View 59 | GetTemplate (); 60 | 61 |- 62 | 63 | 64 | Return the structure of this view (initialization, called once) 65 |
66 | 67 | 68 |
69 | - 70 |
71 | 72 | c4_CustomViewer (); 73 | 74 |- 75 | 76 | 77 | Constructor, must be overriden in derived class 78 |
79 | 80 | 81 |
82 | - 83 |
84 | virtual 85 | ~c4_CustomViewer (); 86 | 87 |- 88 | 89 | 90 | Destructor 91 |
92 | 93 | 94 |
- 44 |
97 | class 98 | c4_CustomViewer 99 | 100 | 101 | 102 | -------------------------------------------------------------------------------- /tcl/tclconfig/install-sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | # 4 | # install - install a program, script, or datafile 5 | # This comes from X11R5; it is not part of GNU. 6 | # 7 | # $XConsortium: install.sh,v 1.2 89/12/18 14:47:22 jim Exp $ 8 | # 9 | # This script is compatible with the BSD install script, but was written 10 | # from scratch. 11 | # 12 | 13 | 14 | # set DOITPROG to echo to test this script 15 | 16 | # Don't use :- since 4.3BSD and earlier shells don't like it. 17 | doit="${DOITPROG-}" 18 | 19 | 20 | # put in absolute paths if you don't have them in your path; or use env. vars. 21 | 22 | mvprog="${MVPROG-mv}" 23 | cpprog="${CPPROG-cp}" 24 | chmodprog="${CHMODPROG-chmod}" 25 | chownprog="${CHOWNPROG-chown}" 26 | chgrpprog="${CHGRPPROG-chgrp}" 27 | stripprog="${STRIPPROG-strip}" 28 | rmprog="${RMPROG-rm}" 29 | 30 | instcmd="$mvprog" 31 | chmodcmd="" 32 | chowncmd="" 33 | chgrpcmd="" 34 | stripcmd="" 35 | rmcmd="$rmprog -f" 36 | mvcmd="$mvprog" 37 | src="" 38 | dst="" 39 | 40 | while [ x"$1" != x ]; do 41 | case $1 in 42 | -c) instcmd="$cpprog" 43 | shift 44 | continue;; 45 | 46 | -m) chmodcmd="$chmodprog $2" 47 | shift 48 | shift 49 | continue;; 50 | 51 | -o) chowncmd="$chownprog $2" 52 | shift 53 | shift 54 | continue;; 55 | 56 | -g) chgrpcmd="$chgrpprog $2" 57 | shift 58 | shift 59 | continue;; 60 | 61 | -s) stripcmd="$stripprog" 62 | shift 63 | continue;; 64 | 65 | *) if [ x"$src" = x ] 66 | then 67 | src=$1 68 | else 69 | dst=$1 70 | fi 71 | shift 72 | continue;; 73 | esac 74 | done 75 | 76 | if [ x"$src" = x ] 77 | then 78 | echo "install: no input file specified" 79 | exit 1 80 | fi 81 | 82 | if [ x"$dst" = x ] 83 | then 84 | echo "install: no destination specified" 85 | exit 1 86 | fi 87 | 88 | 89 | # If destination is a directory, append the input filename; if your system 90 | # does not like double slashes in filenames, you may need to add some logic 91 | 92 | if [ -d $dst ] 93 | then 94 | dst="$dst"/`basename $src` 95 | fi 96 | 97 | # Make a temp file name in the proper directory. 98 | 99 | dstdir=`dirname $dst` 100 | dsttmp=$dstdir/#inst.$$# 101 | 102 | # Move or copy the file name to the temp name 103 | 104 | $doit $instcmd $src $dsttmp 105 | 106 | # and set any options; do chmod last to preserve setuid bits 107 | 108 | if [ x"$chowncmd" != x ]; then $doit $chowncmd $dsttmp; fi 109 | if [ x"$chgrpcmd" != x ]; then $doit $chgrpcmd $dsttmp; fi 110 | if [ x"$stripcmd" != x ]; then $doit $stripcmd $dsttmp; fi 111 | if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dsttmp; fi 112 | 113 | # Now rename the file to the real destination. 114 | 115 | $doit $rmcmd $dst 116 | $doit $mvcmd $dsttmp $dst 117 | 118 | 119 | exit 0 120 | -------------------------------------------------------------------------------- /doc/api/doc_struct.html: -------------------------------------------------------------------------------- 1 | 2 |
9 | Metakit sample code - Struct
10 | 11 |
This application highlights some low-level aspects of the Metakit library. 12 |
13 | 14 |What it does: Struct is a little utility which displays the data 15 | structure of any Metakit datafile on standard output. The output uses a 16 | text-mode graph to display the data structure, which can be useful to determine 17 | what information is stored in a specific Metakit datafile.
18 | 19 |What it illustrates: For demonstration purposes, Struct has been 20 | compiled as a real-mode small-model MS-DOS utility program. It shows how you can extract 21 | structural information from a Metakit datafile without knowing anything 22 | about it. The sample code includes a general "StructureMap" class 23 | to generate text-based graphs. The size of the STRUCT.EXE program demonstrates 24 | how small a fully self-contained application using Metakit can be.
25 | 26 |Note that although Struct must respect the very severe 64 K memory limit imposed 27 | by small-model MS-DOS, you can still use this program to examine the structure of files 28 | of any reasonable size. The reason for this is that Metakit implements on-demand loading, 29 | and that Struct never accesses the actual data itself.
30 | 31 |How to use it: To examine the structure of a datafile, simply 32 | run STRUCT.EXE from the MS-DOS prompt with the filename as argument. There 33 | are a few command-line options to control the output format, these are 34 | listed when you start Struct without a filename. They are:
35 | 36 |-
37 |
- -d
- Show a linear description instead of the default tree. 39 |
- -t
- Show a linear description of the structure, omitting the property names. 40 |
- -c
- Show column structure instead of the deafult tree structure (advanced). 41 |
-
38 |
You can redirect the output to file, just as with any other MS-DOS program. 45 |
46 | 47 |Known problems: None.
48 | 49 |Files in EXAMPLES\STRUCT:
50 | 51 |STRUCT.CPP - Struct main program
52 |
STRUCT.MAK - MSVC 1.52 project makefile
56 | || 57 | Roadmap 58 | Class Index 59 | Sample Index 60 | || 61 | Introduction 62 | Tips and Tricks 63 | || 64 | 65 |
-
5 |
6 | class c4_MemoRef
7 | : public c4_Reference
8 | 9 | -
10 | Used to get or set memo values (growable large binary objects).
11 | 12 | 13 |
| 19 | Public members 20 | | 21 ||
| 25 | 26 | | 27 |
28 | 33 | Constructor 34 | |
35 |
| 39 | operator 40 | | 41 |
42 | 47 | Get the value as binary object 48 | |
49 |
| 53 | c4_MemoRef& 54 | | 55 |
56 | 61 | Set the value to the specified binary object 62 | |
63 |
| 67 | c4_Bytes 68 | | 69 |
70 | 75 | Fetch data from the memo field, up to end if length is zero 76 | |
77 |
| 81 | bool 82 | | 83 |
84 | 89 | Store data, resize by diff_ bytes, return true if successful 90 | |
91 |
101 | 102 |
| 105 | Header file 106 | | 107 |108 | "mk4.h" -- Dec 9, 1999 109 | | 110 |
| 117 | Derived from 118 | | 119 |120 | 121 | c4_Reference 122 | 123 | | 124 |
9 | Metakit sample code - Dump
10 | 11 |
This application is a generic utility for the Metakit library.
12 | 13 |What it does: Dump is a utility program which displays the contents 14 | of a Metakit datafile on standard output. The output shows all the information 15 | which is stored in the datafile, which can be quite useful while developing 16 | and debugging applications based on Metakit.
17 | 18 |What it illustrates: Dump is a so-called "32-bit console 19 | application", this is the modern version of the classical MS-DOS command-line 20 | executables. It shows how you can extract structural information from a 21 | Metakit datafile without knowing anything about it. The basic trick is 22 | to simply open the file, and then to step through each of the properties 23 | (using the members NumProperties and NthProperty). The executable file 24 | is tiny, because both Metakit and MFC have been linked as DLLs.
25 | 26 |How to use it: To dump a datafile, you can start DUMP.EXE from 27 | the MS-DOS prompt with the filename as argument (or drop a file on it in 28 | the Explorer). Since datafiles can store arbitrarily nested data structures, 29 | you may need to examine the output to understand how the information is 30 | presented on standard output. Dump adds quite a bit of detail to guide 31 | you (including all the property names). Basically, the data structure is 32 | traversed recursively, with indentation added to reflect the current nesting 33 | level. There are a number of command-line options to modify the default 34 | output style:
35 | 36 |-
37 |
- -s
- List all tables and subtable, but omit the actual data values. 39 |
- -d
- List all tables and subtables, including a low-level data dump. 40 |
- -f
- Only list all the fields (properties) and their structure. 41 |
- -w
- Wait for the RETURN key just before exiting. 42 |
-
38 |
You can redirect the output to file, just like any other console application. 46 |
47 | 48 |Known problems: None. Note that this is a 32-bit application 49 | which requires Windows 95 (or perhaps Windows NT or Win32s), and that the 50 | Metakit DLLs are used.
51 | 52 |Files in EXAMPLES\DUMP:
53 | 54 |DUMP.CPP - Dump main program
55 |
DUMP.MAK, DUMP.MDP - MSVC 4.2 project makefiles for Win32
59 | || 60 | Roadmap 61 | Class Index 62 | Sample Index 63 | || 64 | Introduction 65 | Tips and Tricks 66 | || 67 | 68 |