Bug in TYPE_FULL ???
Mildred Ki'Lya
ml.mildred593 at gmail.com
Thu Aug 6 13:21:55 UTC 2009
Hi,
I found something quite disturbing in TYPE_FULL (while grepping through
the source tree):
Section TYPE
+ flag:UINTEGER_8;
// 7 6 5 4 3 2 1 0
// | | | | | +- 0:Reference / 1:Expanded
// | | | | +--- 0:Reference / 1:Expanded (by default)
// | | | +----- 0:Normal / 1:Strict
// | | +------- 0:Normal / 1:Strict (by default)
// | +--------- 0:Normal / 1:Temporary
// +----------- 0:Normal / 1:Old generic
Section Public
- expanded_bit :UINTEGER_8 := 000001b;
- default_expanded_bit:UINTEGER_8 := 000010b;
- strict_bit :UINTEGER_8 := 000100b;
- default_strict_bit :UINTEGER_8 := 001000b;
- expanded_ref_bit :UINTEGER_8 := 010000b;
- generic_bit :UINTEGER_8 := 100000b;
//
// Access.
//
- is_expanded :BOOLEAN <- (flag & expanded_bit ) != 0;
- is_default_expanded :BOOLEAN <- (flag & default_expanded_bit) != 0;
- is_strict :BOOLEAN <- (flag & strict_bit ) != 0;
- is_default_strict :BOOLEAN <- (flag & default_expanded_bit) != 0;
- is_expanded_ref :BOOLEAN <- (flag & expanded_ref_bit ) != 0;
- is_generic :BOOLEAN <- (flag & generic_bit ) != 0;
I think you got the ideas, flags.
Now, what bothers me is the following slot:
- is_default_strict :BOOLEAN <- (flag & default_expanded_bit) != 0;
I think it should be:
- is_default_strict :BOOLEAN <- (flag & default_strict_bit ) != 0;
What do you think ?
--
Mildred Ki'Lya
╭───────── mildred593@online.fr ──────────
│ Jabber, GoogleTalk: <mildred at jabber.fr>
│ Website: <http://ki.lya.online.fr> GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/lisaac-devel/attachments/20090806/981e68aa/attachment.pgp>
More information about the Lisaac-devel
mailing list