Displaying 11 results from an estimated 11 matches for "parameterlist".
2010 Nov 01
2
number of items to replace is not a multiple of replacement length
...items to replace in this instance seem to me and
should be an exact copy of the
replacement, save that the number 0 in this particular instance is to be
replaced with the number 58.
If I print the variables in question I get this: (added some tabs to allign
the columns for readability)
>print(parameterList[aCounter, 3])
[[1]]
[,1]
[,2] [,3] [,4]
exampleSingleSelect "Insert single selection box title here"
"SingleSelect" 1 List,3
exampleSlider "Insert slider bar title here"
"Slider&...
2010 Sep 06
2
[LLVMdev] More DIFactory questions - still stumped
...nType()));
if (type->selfParam() != NULL) {
const ParameterDefn * param = type->selfParam();
// genDIParameterType() calls genDIType and then makes it a pointer
// if the underlying type is a reference type.
args.push_back(genDIParameterType(param->type()));
}
const ParameterList & params = type->params();
for (ParameterList::const_iterator it = params.begin(); it !=
params.end(); ++it) {
const ParameterDefn * param = *it;
args.push_back(genDIParameterType(param->type()));
}
DICompositeType fnType = dbgFactory_.CreateCompositeType(
dwarf::DW_T...
2010 Sep 05
2
[LLVMdev] More DIFactory questions - still stumped
...ming we're talking about DIEs
> of type DW_TAG_formal_parameter. However, when I look in the code in
> CGDebugInfo.cpp in clang, I see that the arguments are in fact the bare
> types, not the formal parameter declarations.
>
> Here's what my code looks like:
>
> const ParameterList & params = type->params();
> for (ParameterList::const_iterator it = params.begin(); it !=
> params.end(); ++it) {
> const ParameterDefn * param = *it;
> DIType ptype = genDIParameterType(param->type());
> ptype = dbgFactory_.CreateDerivedTypeEx(
>...
2010 Aug 31
0
[LLVMdev] More DIFactory questions
On Aug 31, 2010, at 9:03 AM, Talin wrote:
> 4) What is the meaning of the "inlinedAt" argument for DebugLoc::get()? Does it mean the location where the inlined code was defined, or the location where it was expanded?
the location where it was expanded
-
Devang
2010 Sep 07
0
[LLVMdev] More DIFactory questions - still stumped
...ly difference from what I'm doing is that I only export debug
symbols in definitions, not declarations. I may be doing wrong,
though, for multi-file compilation (haven't tested thoroughly).
> DICompositeType CodeGenerator::genDIFunctionType(const FunctionType * type)
(...)
> for (ParameterList::const_iterator it = params.begin(); it !=
> params.end(); ++it) {
> const ParameterDefn * param = *it;
> args.push_back(genDIParameterType(param->type()));
> }
Don't do that. I know it looks right, but it's broken in DIFactory.
> DICompositeType fnType = db...
2010 Sep 05
0
[LLVMdev] More DIFactory questions - still stumped
On 5 September 2010 19:32, Talin <viridia at gmail.com> wrote:
> I've carefully studied the source code of CGDebugInfo in clang as a working
> example. One puzzlement is that there's a discrepancy between what the
> "source level debugging with LLVM" docs say and what clang does: According
> to the docs, DW_TAG_formal_parameter is used to specify a formal
2006 Feb 09
22
Length of parameters in Autocompleter.Local()
Hi,
I''m using PHP to fill my parameterlist for Autocompleter.Local as
shown in the example
(http://wiki.script.aculo.us/scriptaculous/show/Autocompleter.Local).
<script type="text/javascript">
new Autocompleter.Local(''recipeNameAlternative'', ''rezept_list'', [
<?php $ende = count($reze...
2010 Sep 07
2
[LLVMdev] More DIFactory questions - still stumped
...hat I only export debug
> symbols in definitions, not declarations. I may be doing wrong,
> though, for multi-file compilation (haven't tested thoroughly).
>
>
>
> > DICompositeType CodeGenerator::genDIFunctionType(const FunctionType *
> type)
> (...)
> > for (ParameterList::const_iterator it = params.begin(); it !=
> > params.end(); ++it) {
> > const ParameterDefn * param = *it;
> > args.push_back(genDIParameterType(param->type()));
> > }
>
> Don't do that. I know it looks right, but it's broken in DIFactory.
>
&g...
2010 Aug 31
5
[LLVMdev] More DIFactory questions
Here are some issues that I am unclear about. What would be great is if the
answers could be incorporated into the comments and documentation for
DIFactory and DebugInfo.h:
1) What types of DIScope are valid arguments for DebugLoc::get()? The method
takes an MDNode* argument, so looking at the function signature is no help.
For example, DIFile is a subtype of DIScope, however looking
at
2010 Sep 07
0
[LLVMdev] More DIFactory questions - still stumped
...that I only export debug
> symbols in definitions, not declarations. I may be doing wrong,
> though, for multi-file compilation (haven't tested thoroughly).
>
>
>
> > DICompositeType CodeGenerator::genDIFunctionType(const FunctionType * type)
> (...)
> > for (ParameterList::const_iterator it = params.begin(); it !=
> > params.end(); ++it) {
> > const ParameterDefn * param = *it;
> > args.push_back(genDIParameterType(param->type()));
> > }
>
> Don't do that. I know it looks right, but it's broken in DIFactory.
>...
2009 Jan 02
0
[LLVMdev] TableGen crash
...Indent << "E = " << D.GenVariableName() << ".end(); B != E; ++B)\n"
<< Indent << Indent1 << "vec.push_back(\"" << Name << "\" + "
<< "*B);\n";
break;
case OptionType::ParameterList:
O << Indent;
O << "for (";
O << D.GenTypeDeclaration();
O << "::iterator B = ";
O << D.GenVariableName();
O << ".begin(),\n";
O << Indent;
O << "E = ";
O << D.GenVariab...