1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
/*************************************************************************
This project implements a complete(!) JPEG (Recommendation ITU-T
T.81 | ISO/IEC 10918-1) codec, plus a library that can be used to
encode and decode JPEG streams.
It also implements ISO/IEC 18477 aka JPEG XT which is an extension
towards intermediate, high-dynamic-range lossy and lossless coding
of JPEG. In specific, it supports ISO/IEC 18477-3/-6/-7/-8 encoding.
Note that only Profiles C and D of ISO/IEC 18477-7 are supported
here. Check the JPEG XT reference software for a full implementation
of ISO/IEC 18477-7.
Copyright (C) 2012-2018 Thomas Richter, University of Stuttgart and
Accusoft. (C) 2019-2020 Thomas Richter, Fraunhofer IIS.
This program is available under two licenses, GPLv3 and the ITU
Software licence Annex A Option 2, RAND conditions.
For the full text of the GPU license option, see README.license.gpl.
For the full text of the ITU license option, see README.license.itu.
You may freely select between these two options.
For the GPL option, please note the following:
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
*************************************************************************/
/*
* Customizable hooks.
*
* $Id: hooks.hpp,v 1.8 2014/09/30 08:33:17 thor Exp $
*
* Hooks provide a standard method to supply call-out functions.
* They are initialized by the client application and called by
* the library. They pass data in terms of tag items.
* They also pass client private data.
*
* This is part of the external interface of the jpeg
* and visible to the outher world.
*/
#ifndef HOOKS_HPP
#define HOOKS_HPP
/// Includes
#include "jpgtypes.hpp"
#include "tagitem.hpp"
///
///
#ifndef JPG_EXPORT
#define JPG_EXPORT
#endif
///
/// Design
/** Design
******************************************************************
** struct J2k_Hook **
** Super Class: none **
** Sub Classes: none **
** Friends: **
******************************************************************
The hook structure defines a generic call-back hook. This allows
the user to "hook" into the library and to get called on certain
events. The j2k lib uses this structure for all its call-back
functions.
A hook defines first an entry point to be called. This callback
function takes a pointer to the hook structure and a tag list
as arguments. Tag lists are discussed in a separate file and
provide enough flexibility to extend options.
The callback function can be one of two kinds, it may either
return a LONG (as a result code) or a generic pointer. The
library uses currently both types, see the documentation which
hook uses which.
Furthermore, hooks provide a "sub entry" point. This is not
used by the library at all, but you may use it. A typical
application would be to let the main entry point point to a
small "stub" function which loads registers, base pointers etc.
and let the "sub entry" point to the real thing.
Last but not least, a hook contains a user data field you may
use for whatever you feel like. Typically, this would be either
a base register, or a pointer to the corresponding base object
the hook is part of.
In a C++ environment, a hook entry would consist of a static
member function of your object, which would forward hook calls
to the non-static methods of the object.
* */
///
/// Hook structure
// this is a function as it is called from the library
// It is called with the hook as one parameter such that the
// client is able to extract its private data.
// It also comes with a tag item parameter to pass data.
struct JPG_EXPORT JPG_Hook {
// The callbacks.
#ifdef __cplusplus
typedef JPG_LONG (LongHookFunction)(struct JPG_Hook *, struct JPG_TagItem *tag);
typedef JPG_APTR (APtrHookFunction)(struct JPG_Hook *, struct JPG_TagItem *tag);
#endif
//
union JPG_EXPORT HookCallOut {
JPG_LONG (*hk_pLongEntry)(struct JPG_Hook *, struct JPG_TagItem *tag); // the main entry point.
JPG_APTR (*hk_pAPtrEntry)(struct JPG_Hook *, struct JPG_TagItem *tag);
//
#ifdef __cplusplus
// Constructors
HookCallOut(LongHookFunction *hook)
: hk_pLongEntry(hook)
{ }
//
HookCallOut(APtrHookFunction *hook)
: hk_pAPtrEntry(hook)
{ }
//
HookCallOut(void)
: hk_pLongEntry(0)
{ }
#endif
//
} hk_Entry,hk_SubEntry;
//
// hk_SubEntry
// can be used by the application to forward the request
// and to load the private data below in whatever register it needs.
// Is otherwise not used by the application.
//
JPG_APTR hk_pData; // for private use of the client.
//
#ifdef __cplusplus
// Constructors
JPG_Hook(LongHookFunction *hook = 0, JPG_APTR data = 0)
: hk_Entry(hook), hk_pData(data)
{ }
//
JPG_Hook(APtrHookFunction *hook, JPG_APTR data = 0)
: hk_Entry(hook), hk_pData(data)
{ }
//
//
JPG_LONG CallLong(struct JPG_TagItem *tag)
{
return (*hk_Entry.hk_pLongEntry)(this,tag);
}
//
JPG_APTR CallAPtr(struct JPG_TagItem *tag)
{
return (*hk_Entry.hk_pAPtrEntry)(this,tag);
}
#endif
//
};
///
///
#endif
|
