Raw content of Bio::EnsEMBL::Funcgen::Parsers::GFF#
# EnsEMBL module for Bio::EnsEMBL::Funcgen::Parsers::GFF
#
#Could this be based on a Generic Flat file parser?
=head1 NAME
Bio::EnsEMBL::Funcgen::Parsers::GFF
=head1 SYNOPSIS
my $parser_type = "Bio::EnsEMBL::Funcgen::Parsers::GFF";
push @INC, $parser_type;
my $imp = $class->SUPER::new(@_);
=head1 DESCRIPTION
This is a definitions class which should not be instatiated directly, it
normally set by the Importer as the parent class. GFF contains meta
data and methods specific to data in bed format, to aid
parsing and importing of experimental data.
=head1 AUTHOR
This module was created by Nathan Johnson.
=head1 CONTACT
Post questions to the EnsEMBL development list ensembl-dev@ebi.ac.uk
=head1 METHODS
=cut
package Bio::EnsEMBL::Funcgen::Parsers::GFF;
use Bio::EnsEMBL::Utils::Exception qw( throw warning deprecate );
use Bio::EnsEMBL::Utils::Argument qw( rearrange );
use strict;
use vars qw(@ISA);
@ISA = qw(Bio::EnsEMBL::Funcgen::Parsers::Simple);
=head2 new
Example : my $self = $class->SUPER::new(@_);
Description: Constructor method for GFF class
Returntype : Bio::EnsEMBL::Funcgen::Parsers::GFF
Exceptions : None
Caller : Bio::EnsEMBL::Funcgen::Importer
Status : at risk
=cut
sub new{
my $caller = shift;
my $class = ref($caller) || $caller;
#define default fields here and pass
#We also need to be able to take custom attrs mappings
#keys are array index of field, key are Feature paramter names
#reverse this?
#Unless we have a compound field which we name accordingly
#And then call e.g. parse_attrs
#Which will return a hash with the relevant Feature attributes
#Is splitting this up simply going to make the parse slower due to acessor methods?
#Pass or just set directly here?
#