search for: argument_list

...ke \S4method{<myMethod>}{<ClassOf1stArgToDispatch>, <ClassOf2ndArgToDispatch>}(<Name1stArgToDispatch>,<Name2ndArgToDispatch>) i.e. if I insert a line break in the Rd file after any item of the signature_list argument to \S4method. Using line breaks in the the third (argument_list) argument is not a problem, though. So my little RFE would be to ask you to allow some optional line breaking mechanism for the second argument of \S4method, too, if this is not too hard to achieve. Best regards Peter

...t;id> >> attribute_list := <attribute> ( <attribute>)* >> attribute := <name> (= <value>)? >> | <attribuge_id> >> >> … >> >> function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> >> > So something like this (no references inside of the 'attributes' statement allowed, cf. above)? > > attributes #1 = { noinline, alignstack=4 } > attributes #2 = { "no-sse" } > > define void @foo() #1 #2 { ret void } >...

...> attrgroup_id := #<id> > attribute_list := <attribute> ( <attribute>)* > attribute := <name> (= <value>)? > | <attribuge_id> > > … > > function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> > So something like this (no references inside of the 'attributes' statement allowed, cf. above)? attributes #1 = { noinline, alignstack=4 } attributes #2 = { "no-sse" } define void @foo() #1 #2 { ret void } This seems reasonable to me. >>...

...up_id> = { <attribute_list> } attrgroup_id := #<id> attribute_list := <attribute> ( <attribute>)* attribute := <name> (= <value>)? | <attribuge_id> … function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> > Target-Dependent Attributes in IR > --------------------------------- > > The front-end is responsible for knowing which target-dependent options are > interesting to the target. Target-dependent attributes are specified as strings, > which are under...

Ein eingebundener Text mit undefiniertem Zeichensatz wurde abgetrennt. Name: nicht verf?gbar URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20101220/d04ff621/attachment.pl>

Hi! This is a proposal to expand the Attributes class to support many different options that will be accessible by all parts of the compiler. Please read and give any feedback you may have. Thanks! -bw Passing Options to Different Parts of the Compiler Problem ======= There is a growing need to pass information from the front-end to different parts of the compiler, especially

...> attrgroup_id := #<id> > attribute_list := <attribute> ( <attribute>)* > attribute := <name> (= <value>)? > | <attribuge_id> > > … > > function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> > > >> Target-Dependent Attributes in IR >> --------------------------------- >> >> The front-end is responsible for knowing which target-dependent options are >> interesting to the target. Target-dependent attributes are specified as str...