search for: infofile

...) as follows, I get an error: > wet.bnd <- get.bnddata("wetlands\\info", "WETLANDS.BND") Error in get.bnddata("wetlands\\info", "WETLANDS.BND") : Couldn't open table get.tablenames() shows that the table exists TableName InfoFile NFields RecSize NRecords External 1 WETLANDS.BND ARC0000 1 16 1 FALSE 2 WETLANDS.PAT ARC0001 1 26 355 FALSE 3 WETLANDS.TIC and if I use get.tabledata() the table will open (but the values are set to zero) > wet.bnd...

...13") Number of ARCS:16723 Number of CENTROIDS:1625 Number of LABELS:1624 Number of POLYGONS:1625 Number of TOLERANCES:10 > attach(d) > plotpal(arc, pal) > newarc<-thinlines(arc,.05) > plotpal(newarc, pal) > get.tablenames("info/") TableName InfoFile NFields RecSize NRecords External 1 TR13.AAT ARC0001 1 38 16723 TRUE 2 TR13.BND ARC0002 1 32 1 FALSE 3 TR13.PAT ARC0003 1 178 1625 FALSE 4 TR13.TIC...

Hi Trevor, DWARF exception handling is an amalgam of several different documents and code tables, which all conspire to give us exception handling. :-) The documents you should read are: * Exception Handling Tables (http://www.codesourcery.com/public/cxx-abi/exceptions.pdf) This explains in detail what the table in the "__TEXT,__gcc_except_tab" section is all about. * DWARF

Hi, I'm trying to learn all that I can about exception handling from the compiler's point of view. Although much has been written about compiler theory in general -- parsing, code generation, you name it -- I can find almost nothing on the specific problem of exception handling support. In fact, the most informative document I've been able to find so far is "Bill's

Hi, I''m trying to configure IMQ to work on the same machine with frottle (http://frottle.sourceforge.net). The problem is both feed themselves packets through netfilter queueing mechanism, but currently there can only be one netfilter queue per protocol family. To explain why I need IMQ in the first place I have to explain what frottle does. It is a deamon that tweaks the behaviour of a