On 3 November 2013 18:34, George R Goffe wrote:
> Hi,
>
> I've been seeing a lot of these messages. I'm building from the repository
> (main trunk?) as of 1 hour ago or so (fairly up to date I think).
>
> Am I doing something wrong? Is this a bug?
(Your question would probably be more appropriate
2009/4/14 Arthur Schwarz:
> --- On Mon, 4/13/09, Joe Buck wrote:
>
> them all.
>>
>> Consider
>>
>> #include
>> struct Foo { int bar;};
>> int main() {
>> std::cerr << Foo();
>> }
>>
>> Try it, the result is ugly, and I often encounter this one
>
> (Personal opinion - not to be construed as wi
On Mon, Apr 13, 2009 at 05:10:23PM -0700, Dave Korn wrote:
> Joe Buck wrote:
>
> > And this, of course, means we have to define relevance. There are two
> > cases: the first is when we fail to choose an overload because of
> > ambiguity; there we can just report all of the choices that are tied f
>
> So I guess, yes, I'm asking Arthur to suggest rules
> of relevance that would
> enable the compiler to decide what kind of user error is
> implied by a given
> syntax error.
>
> cheers,
> DaveK
>
You're asking for a lot. I've never been accused of being smart (the quip
being,
Joe Buck wrote:
> And this, of course, means we have to define relevance. There are two
> cases: the first is when we fail to choose an overload because of
> ambiguity; there we can just report all of the choices that are tied for
> "equally good". The other case is where no overload matches. T
--- On Mon, 4/13/09, Joe Buck wrote:
them all.
>
> Consider
>
> #include
> struct Foo { int bar;};
> int main() {
> std::cerr << Foo();
> }
>
> Try it, the result is ugly, and I often encounter this one
(Personal opinion - not to be construed as wisdom).
The issue with the result i
> > Thanks Dave;'
> >
> > Acerbic comments below.
>
> >> Isn't that exactly what the
> compiler IS doing, as
> >> indicated by "candidates are ... "?
> >
> > I don't think so. [ ... ] A clear
> message that arg is wrong I think
> > is a better approach.
>
> But maybe arg is right an
On Mon, Apr 13, 2009 at 03:53:04PM -0700, Dave Korn wrote:
> Nonono; I didn't mean to impugn anything you're doing, just trying to point
> out that it's not easy. Your suggestions are all valid and good ideas, but
> before they can be usefully incorporated into the compiler, they need to be
> ex
Arthur Schwarz wrote:
> Thanks Dave;'
>
> Acerbic comments below.
G'wan, I can take it!
>> Isn't that exactly what the compiler IS doing, as
>> indicated by "candidates are ... "?
>
> I don't think so. [ ... ] A clear message that arg is wrong I think
> is a better approach.
But may
Thanks Dave;'
Acerbic comments below.
--- On Mon, 4/13/09, Dave Korn wrote:
> > using namespace std;
> > void CommandLine(int argc, char** argv);
> > int main(int argc, char** argv) {
> > string a = "output.txt";
> > string* b = &a;
> > ofstream y;
> >
> y.open("output.txt", ios
Arthur Schwarz wrote:
> using namespace std;
> void CommandLine(int argc, char** argv);
> int main(int argc, char** argv) {
>string a = "output.txt";
>string* b = &a;
>ofstream y;
>y.open("output.txt", ios::in);
>y.open( a, ios::in);
>y.open( a.c_str(), i
On Wed, 2006-12-06 at 17:19 +0100, Come Lonfils wrote:
> Hi,
> I'm trying to know more about how messages are send to the objects in
> objective-C
Messages are send via a dynamic lookup using strings.
For the GNU runtime, objc_msg_lookup is called to get the function
pointer and then we cast it to
Hi,
I'm trying to know more about how messages are send to the
objects in objective-C, how they are store,...
In which structures en how?
Where should I look in the source code of gcc to know it?
I looked in libobjc but I'm a bit lost.
Thanks very much
See How Messaging Works document at
http
On Dec 6, 2006, at 8:19 AM, Come Lonfils wrote:
I'm trying to know more about how messages are send to the objects
in objective-C, how they are store,...
In which structures en how?
Where should I look in the source code of gcc to know it? I looked
in libobjc but I'm a bit lost.
I'd probabl
14 matches
Mail list logo
