Abstract: The present invention provides a system and/or method that facilitates programming within Common Language Runtime (CLR) for a C++ programmer by employing a mixed type. An inheritance component creates the mixed type from received code such that the mixed class type is allocated into memory into a pure native part and a pure managed part. Furthermore, construction, destruction and function calls for mixed types are provided facilitating programming within Common Language Runtime (CLR).

Abstract: The present invention provides a system and/or method that facilitates expanding keywords within an existing computer programming language by employing a whitespace keyword containing embedded whitespace. A whitespace component can receive code, and create a whitespace keyword based at least upon a successive comparison of adjacent tokens. The whitespace component creates a whitespace keyword by replacing more than one token with a single token containing embedded whitespace. Moreover, the whitespace component can utilize a lexical analyzer to group code into tokens and a parser component to parse the code.

Abstract: An independent distributed database system comprising a plurality of sites wherein all users at all sites work off-line with local data. All application transactions are against the local database only, and every site stores “all and only” the data it needs. On-line transactions occur only in the background, including a periodical “synch” between sites that transmits any changes to data of interest to that site. If the background operations are interrupted or the network is temporarily unavailable, the user does not see new changes made at other sites until the data link is available again, but is otherwise unaffected. It is a feature that no site acts as a “server” for any other site. Some sites may store more data or have more users than others, but all sites are logically peers.

Abstract: An independent distributed database system comprising a plurality of sites wherein all users at all sites work off-line with local data. All application transactions are against the local database only, and every site stores "all and only" the data it needs. On-line transactions occur only in the background, including a periodical "synch" between sites that transmits any changes to data of interest to that site. If the background operations are interrupted or the network is temporarily unavailable, the user does not see new changes made at other sites until the data link is available again, but is otherwise unaffected. It is a feature that no site acts as a "server" for any other site. Some sites may store more data or have more users than others, but all sites are logically peers.