search for: attribute_list

...) A less compelling (but IMHO valid) argument is that it makes the internal representation of attributes that much more complex. Fair enough. >> In other words, I think something like the following might be nicer: >> >> attribute_group := attributes <attrgroup_id> = { <attribute_list> } >> attrgroup_id := #<id> >> attribute_list := <attribute> ( <attribute>)* >> attribute := <name> (= <value>)? >> | <attribuge_id> >> >> … >> >> function_def := <attribute_list&...

...is the idea of an "attribute group". As the name > implies, it's a group of attributes that are then referenced by objects within > the IR. An attribute group is a module-level object. The BNF of the syntax is: > > attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } > attrgroup_id := #<number> > attribute_list := <attribute> (, <attribute>)* > attribute := <name> (= <value>)? > > To use an attribute group, an object references the attribute group's ID: > > attribute_group_ref := attrgroup...

...n "attribute group". As the name >> implies, it's a group of attributes that are then referenced by objects within >> the IR. An attribute group is a module-level object. The BNF of the syntax is: >> >> attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } >> attrgroup_id := #<number> >> attribute_list := <attribute> (, <attribute>)* >> attribute := <name> (= <value>)? >> >> To use an attribute group, an object references the attribute group's ID: >> >> attr...

...an "attribute group". As the name >> implies, it's a group of attributes that are then referenced by objects within >> the IR. An attribute group is a module-level object. The BNF of the syntax is: >> >> attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } >> attrgroup_id := #<number> >> attribute_list := <attribute> (, <attribute>)* >> attribute := <name> (= <value>)? >> >> To use an attribute group, an object references the attribute group's ID: >> >> attrib...

...e of this proposal is the idea of an "attribute group". As the name implies, it's a group of attributes that are then referenced by objects within the IR. An attribute group is a module-level object. The BNF of the syntax is: attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } attrgroup_id := #<number> attribute_list := <attribute> (, <attribute>)* attribute := <name> (= <value>)? To use an attribute group, an object references the attribute group's ID: attribute_group_ref := attrgroup(<attrgroup_id>) This is...

Hi all, - There is a worth thing to note about these changes, which is the handling of $ATTRIBUTE_LIST attribute, that is rare attribute. When there are a lot of attributes and there is no more space in the MFT record, all those attributes that can be made non-resident are moved out the MFT, so this is where the $ATTRIBUTE_LIST comes in. - Most people must have seen the ugly "EDD error&quo...

...the idea of an "attribute group". As the name implies, it's a group of attributes that are then referenced by objects within the IR. An attribute group is a module-level object. The BNF of the syntax is: attribute_group := <attrgroup_id> '=' attributes '{' <attribute_list> '}' attrgroup_id := #<id> attribute_list := <attribute> <attribute>* attribute := <name> ('=' <list_of_values>)? list_of_values := <value> | '(' <value> <value>* ')' id := <numbe...

...t;attribute group". As the name > implies, it's a group of attributes that are then referenced by objects within > the IR. An attribute group is a module-level object. The BNF of the syntax is: > > attribute_group := <attrgroup_id> '=' attributes '{' <attribute_list> '}' > attrgroup_id := #<id> > attribute_list := <attribute> <attribute>* > attribute := <name> ('=' <list_of_values>)? > list_of_values := <value> | '(' <value> <value>* ')' > id...

...up". As the name >> implies, it's a group of attributes that are then referenced by objects within >> the IR. An attribute group is a module-level object. The BNF of the syntax is: >> >> attribute_group := <attrgroup_id> '=' attributes '{' <attribute_list> '}' >> attrgroup_id := #<id> >> attribute_list := <attribute> <attribute>* >> attribute := <name> ('=' <list_of_values>)? >> list_of_values := <value> | '(' <value> <value>* ')' &g...

...a of an "attribute group". As the name > implies, it's a group of attributes that are then referenced by objects > within > the IR. An attribute group is a module-level object. The BNF of the syntax > is: > > attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } > attrgroup_id := #<number> > attribute_list := <attribute> (, <attribute>)* > attribute := <name> (= <value>)? > > To use an attribute group, an object references the attribute group's ID: > > attribute_group_ref := attrgro...

Dear all, I have used Markdown via Drupal a few months now, with a customer site and my currently my own blog and based on that practical experience I wanted to add some extra functionality to PHP Markdown Extra, so out of this grow my (extended) weekend project https://github.com/egil/php-markdown-extra-extended The big missing item right now that I would like to implement is the ability to add

Patch ready for merging. v4: - check return code of tsk_fs_attr_walk - pass TSK_FS_FILE_WALK_FLAG_NOSPARSE as additional flag to tsk_fs_attr_walk After discussing with TSK authors the behaviour is clear. [1] In case of COMPRESSED blocks, the callback will be called for all the attributes no matter whether they are on disk or not (sparse). In such cases, the block address will be 0. [2] So

Hi folks, I expect that the response to this post will be "we don't need such a thing", but humour me for a moment by pretending that in fact we do. HTML5 added a number of new tags to the mix, but arguably the most significant is the `time` element. It associates a machine-readable timestamp with a human-readable string (e.g. `<time