Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
LabComm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Tommy Olofsson
LabComm
Commits
1c11e3c9
Commit
1c11e3c9
authored
10 years ago
by
Sven Gestegård Robertz
Browse files
Options
Downloads
Patches
Plain Diff
more on type_defs
parent
f60d2c16
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/tech_report.tex
+20
-8
20 additions, 8 deletions
doc/tech_report.tex
with
20 additions
and
8 deletions
doc/tech_report.tex
+
20
−
8
View file @
1c11e3c9
...
...
@@ -330,11 +330,7 @@ i.e.,
<sample
_
data> <user
_
id: 40> <length: 14> <packed
_
sample
_
data>
\end{verbatim}
\section
{
Technical details
}
TODO: better section title
\subsection
{
Type and sample declarations
}
\section
{
Type and sample declarations
}
LabComm has two constructs for declaring sample types,
\emph
{
sample
declarations
}
and
\emph
{
type declarations
}
. A sample declaration is used
...
...
@@ -386,7 +382,7 @@ come from two independent number series. To identify which
\verb
+
TYPE_DECL
+
a particular
\verb
+
SAMPLE_DECL
+
corresponds to, the
\verb
+
TYPE_BINDING
+
packet is used.
\subs
ubs
ection
{
Example
}
\subsection
{
Example
}
The labcomm declaration
\lstinputlisting
[basicstyle=\footnotesize\ttfamily]
{
../examples/user
_
types/test.lc
}
...
...
@@ -418,6 +414,22 @@ Note that the id 0x40 is used both for the \verb+TYPE_DECL+ of
\verb
+
TYPE_BINDING
+
binds the sample id
\verb
+
0x40
+
to the type id
\verb
+
0x44
+
.
\subsection
{
Run-time behaviour
}
When a sample type is registered on an encoder, a
\verb
+
SAMPLE_DECL
+
(i.e., the flat signature) is always generated on that encoder channel.
If the sample depends on user types (i.e., typedefs),
\verb
+
TYPE_DECL
+
packets are encoded, recursively, for the dependent types and a
corresponding
\verb
+
TYPE_BINDING
+
is encoded.
If a
\verb
+
TYPE_DECL
+
is included via multiple sample types, or
dependency paths, an encoder may choose to only encode it once, but is
not required to do so. However, if multiple
\verb
+
TYPE_DECL
+
packets are
sent for the same
\verb
+
typedef
+
, the encoder must use the same
\verb
+
type_id
+
.
\section
{
Ideas/Discussion
}
:
...
...
@@ -515,8 +527,8 @@ The built-in data types are encoded as follows:
<type
_
binding> |
<sample
_
data> )
<version> := <string>
<sample
_
de
f>
:= <sample
_
id> <string> <type>
<type
_
de
f>
:= <type
_
id> <string> <type>
<sample
_
de
cl>
:= <sample
_
id> <string> <type>
<type
_
de
cl>
:= <type
_
id> <string> <type>
<type
_
binding> := <sample
_
id> <type
_
id>
<user
_
id> := 0x40..0xffffffff
<sample
_
id> : <user
_
id>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment