Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Erwin Data Structures 2.1.88591 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Erwin Data Structures 2.1.88591 (Default branch)
# 1  
Old 08-28-2008
Erwin Data Structures 2.1.88591 (Default branch)
ImageThe Erwin library is a very efficient and robust data structure templatelibrary for C and C++. No templates are used; a Perl script generatesC files. Vectors (dynamic arrays), lists, and hash tables (maps) ofarbitrary key and value types are provided. Several tools are includedfor auto-generating a C interface around C++ libraries, C++ extensionslike slots/properties, symbol (=hashed string) management, sophisticatedassertion macros, and documentation extraction.License: Freely DistributableChanges:
Integer overflows leading to unexpected orderingswere fixed from many comparison functions. CMakesupport was added. Two more bit operations fromHacker's Delight were added.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Programming

Signalsafe data structures

Hello, I have a signal handler which manipulates a data structure. The data structure's operations aren't atomic. So if two threads/processes are in a critical section at the same time the data structure will be broken. With threads you can avoid this stuff with semaphores etc. However,... (10 Replies)
Discussion started by: littlegnome
10 Replies

2. Shell Programming and Scripting

Perl Data Structures

Here is what i need to do. @data #has all column wise data so say info for col 1 location for all rows would be in this array $array = \@data But i need to create a file which should contain these information in a format for all columns even if i have got no values from some of the index... (0 Replies)
Discussion started by: dinjo_jo
0 Replies

3. Programming

shared memory - userdefined data structures

Hello, I wonder if I can write my userdefined data structures(ex: a list) to a shared memory segment? I know, the shm functions get (void*) parameter so I should be able to read and write a list into the shared memory. may someone inform and clarify me about that, please? (1 Reply)
Discussion started by: xyzt
1 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

tangram::type::dump::perl

Tangram::Type::Dump::Perl(3pm)				User Contributed Perl Documentation			    Tangram::Type::Dump::Perl(3pm)

NAME

       Tangram::Type::Dump::Perl - map any Perl object as scalar dump

SYNOPSIS

	  use Tangram::Core;
	  use Tangram::Type::Dump::Perl; # always

	  $schema = Tangram::Schema->new(
	     classes => { NaturalPerson => { fields => {

	     perl_dump =>
	     {
		diary => # diary is a perl hash
		{
		   col => 'diarydata',
		   sql => 'TEXT',
		   indent => 0,
		   terse => 1,
		   purity => 0
		},

		lucky_numbers => 'int', # use defaults
	     }

DESCRIPTION

       Maps arbitrary Perl data structures by serializing to a string representation. The persistent fields are grouped in a hash under the
       "perl_dump" key in the field hash.

       Serialization is done by Data::Dumper, which traverses the Perl data structure and creates a string representation of it. The resulting
       string will be mapped to the DBMS as a scalar value. During restore, the scalar value will be eval'd to reconstruct the original data
       structure.

       As of Tangram 2.07.1, persistent references are safely handled via the Tangram::Type::Dump utility class.

       The field names are passed in a hash that associates a field name with a field descriptor. The field descriptor may be either a hash or a
       string. The hash uses the following fields:

       * col
       * sql
       * indent
       * terse
       * purity

       The optional fields "col" and "sql" specify the column name and the column type for the scalar value in the database. If not present, "col"
       defaults to the field name and "sql" defaults to VARCHAR(255).  Values will be always quoted as they are passed to the database.

       The remaining optional fields control the serialization process. They will be passed down to Data::Dumper as values to the corresponding
       Data::Dumper options. The default settings are: no indentation ("indent=0"), compact format ("terse=1"), and quick dump ("purity=0").

AUTHOR

       This mapping was contributed by Gabor Herr <herr@iti.informatik.tu-darmstadt.de>

perl v5.8.8							    2006-03-29					    Tangram::Type::Dump::Perl(3pm)