head	1.6;
access;
symbols
	LMTP2NNTP_1_4_1:1.6
	LMTP2NNTP_1_4_0:1.6
	VAL_0_9_4:1.6
	VAL_0_9_3:1.6
	LMTP2NNTP_1_3_0:1.6
	LMTP2NNTP_1_3b2:1.6
	LMTP2NNTP_1_3b1:1.6
	LMTP2NNTP_1_3a3:1.6
	LMTP2NNTP_1_3a2:1.6
	LMTP2NNTP_1_3a1:1.6
	VAL_0_9_2:1.6
	VAL_0_9_1:1.6
	LMTP2NNTP_1_2_0:1.5
	LMTP2NNTP_1_2b4:1.5
	LMTP2NNTP_1_2b3:1.5
	LMTP2NNTP_1_2b2:1.5
	LMTP2NNTP_1_2b1:1.5
	LMTP2NNTP_1_2a8:1.5
	LMTP2NNTP_1_2a7:1.5
	LMTP2NNTP_1_2a6:1.5
	LMTP2NNTP_1_2a5:1.5
	VAL_0_9_0:1.4
	LMTP2NNTP_1_2a4:1.4
	LMTP2NNTP_1_2a3:1.4;
locks; strict;
comment	@# @;


1.6
date	2003.02.17.14.35.24;	author rse;	state Exp;
branches;
next	1.5;

1.5
date	2002.05.27.15.34.33;	author rse;	state Exp;
branches;
next	1.4;

1.4
date	2002.01.16.14.09.18;	author rse;	state Exp;
branches;
next	1.3;

1.3
date	2002.01.10.20.05.29;	author rse;	state Exp;
branches;
next	1.2;

1.2
date	2002.01.09.13.44.50;	author rse;	state Exp;
branches;
next	1.1;

1.1
date	2002.01.09.10.44.28;	author rse;	state Exp;
branches;
next	;


desc
@@


1.6
log
@remove trailing whitespaces from source files and apply standard OSSP header to documents
@
text
@   _        ___  ____ ____  ____               _
  |_|_ _   / _ \/ ___/ ___||  _ \  __   ____ _| |
  _|_||_| | | | \___ \___ \| |_) | \ \ / / _` | |
 |_||_|_| | |_| |___) |__) |  __/   \ V / (_| | |
  |_|_|_|  \___/|____/____/|_|       \_/ \__,_|_|

  OSSP val - Value Access

  TODO

  o dynamic variables: function pointer for set/get

  o in combination with var lookups, each variable should have
    dump/print/output feature/function which results the value (integer,
    string, struct, etc.) always as a string (stringify function)

  o access control feature: val_reg(<acl>, ...)
                            val_get(<access-level>, ...)
    for use in combination with var in order to allow all internals to
    be stored and registered in val structure but allow variable lookups
    only to access public/whatever type variables.

@


1.5
log
@remember
@
text
@d1 5
d7 1
a7 2
TODO
----
d9 1
a9 1
o dynamic variables: function pointer for set/get
d11 1
a11 3
o in combination with var lookups, each variable should have dump/print/output
  feature/function which results the value (integer, string, struct, etc.) always as a string
  (stringify function)
d13 9
a21 5
o access control feature: val_reg(<acl>, ...)
                          val_get(<access-level>, ...)
  for use in combination with var in order to allow all internals to be stored
  and registered in val structure but allow variable lookups only to access
  public/whatever type variables.
@


1.4
log
@new OSSP val build environment
@
text
@d5 12
@


1.3
log
@We don't need locking, let the controlling application do such checks instead.

PR:
Submitted by:
Reviewed by:
Approved by:
Obtained from:
@
text
@d4 1
@


1.2
log
@Remember flock(2).

PR:
Submitted by:
Reviewed by:
Approved by:
Obtained from:
@
text
@a3 2

File locking might be enforced, or available as a runtime option.
@


1.1
log
@Create a fresh build environment for new born child OSSP val.
This soon to be written library will provide a user-land val
with O(1) time complexity and fixed size memory usage.
@
text
@d5 1
@