search for: supertyp

Hi.. Guess this is asked alot, looked through the last 1000 posts but couldnt find anything so here goes =) Running a 10 finger training program originally made for win 95 on wine, and it all runs smoothly except that i cant get it to show the danish characters "???", if i press the keys on the keyboard they work fine so its not the keymapping thats wrong.. It just replaces the

...a; struct B b; }; int foo(struct A *a, struct B *b) { .... } void bar() { union u whoops; foo(&whoops.a, &whoops.b); } If you annotated foo with a partial access path, you may or may not get the right answer. You would think your type dag solves this, because you'll see they share a supertype. But it's actually worse than that: file: bar.h union u { struct A a; struct B b; }; int foo(struct A *, struct B*); file: foo.c int foo(struct A *a, struct B *b) { .... } file: bar.c #include "bar.h" void bar() { union u whoops; foo(&whoops.a, &whoops.b); } You w...

On Mar 11, 2013, at 2:37 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > On Mon, Mar 11, 2013 at 2:06 PM, Manman Ren <mren at apple.com> wrote: >> >> On Mar 11, 2013, at 1:17 PM, Daniel Berlin <dberlin at dberlin.org> wrote: >> >>> On Mon, Mar 11, 2013 at 11:41 AM, Manman Ren <mren at apple.com> wrote: >>>> Based on

...> > } > > void bar() { > union u whoops; > foo(&whoops.a, &whoops.b); > } > > If you annotated foo with a partial access path, you may or may not > get the right answer. > You would think your type dag solves this, because you'll see they > share a supertype. > > But it's actually worse than that: > > file: bar.h > union u { > struct A a; > struct B b; > }; > > int foo(struct A *, struct B*); > > file: foo.c > > int foo(struct A *a, struct B *b) { > .... > > } > > file: bar.c > &g...

Hi R-users, I want to apply a function to each column of a data frame that is numeric. Thus I tried to check it for each column first: > apply(df, 2, function(x) is.numeric(x)) A60 A64 A66a A67 A71 A75a A80 A85 A91 A95 A96 A97 A98 A99 FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE

...r() { >> union u whoops; >> foo(&whoops.a, &whoops.b); >> } >> >> If you annotated foo with a partial access path, you may or may not >> get the right answer. >> You would think your type dag solves this, because you'll see they >> share a supertype. >> >> But it's actually worse than that: >> >> file: bar.h >> union u { >> struct A a; >> struct B b; >> }; >> >> int foo(struct A *, struct B*); >> >> file: foo.c >> >> int foo(struct A *a, struct B *b) { &gt...

There has been talks on the User list about registering atleast one MIME type with the IETF for .ogg files. I am familiar with the procedures for this and will start doing it right now unless someone urgently wants me to stop. A discussion concerned wether audio/ogg or application/ogg should be registered, I will most definately register audio/ogg for Ogg Vorbis, and in the future video/ogg may

...; >>> foo(&whoops.a, &whoops.b); >>> } >>> >>> If you annotated foo with a partial access path, you may or may not >>> get the right answer. >>> You would think your type dag solves this, because you'll see they >>> share a supertype. >>> >>> But it's actually worse than that: >>> >>> file: bar.h >>> union u { >>> struct A a; >>> struct B b; >>> }; >>> >>> int foo(struct A *, struct B*); >>> >>> file: foo.c >&...

...;whoops.a, &whoops.b); >>>> } >>>> >>>> If you annotated foo with a partial access path, you may or may not >>>> get the right answer. >>>> You would think your type dag solves this, because you'll see they >>>> share a supertype. >>>> >>>> But it's actually worse than that: >>>> >>>> file: bar.h >>>> union u { >>>> struct A a; >>>> struct B b; >>>> }; >>>> >>>> int foo(struct A *, struct B*); >&gt...

...; >>>>> } >>>>> >>>>> If you annotated foo with a partial access path, you may or may not >>>>> get the right answer. >>>>> You would think your type dag solves this, because you'll see they >>>>> share a supertype. >>>>> >>>>> But it's actually worse than that: >>>>> >>>>> file: bar.h >>>>> union u { >>>>> struct A a; >>>>> struct B b; >>>>> }; >>>>> >>>>&...

...gt; } >>>>>> >>>>>> If you annotated foo with a partial access path, you may or may not >>>>>> get the right answer. >>>>>> You would think your type dag solves this, because you'll see they >>>>>> share a supertype. >>>>>> >>>>>> But it's actually worse than that: >>>>>> >>>>>> file: bar.h >>>>>> union u { >>>>>> struct A a; >>>>>> struct B b; >>>>>> }; >>&...

...;>>> >>>>>>> If you annotated foo with a partial access path, you may or may not >>>>>>> get the right answer. >>>>>>> You would think your type dag solves this, because you'll see they >>>>>>> share a supertype. >>>>>>> >>>>>>> But it's actually worse than that: >>>>>>> >>>>>>> file: bar.h >>>>>>> union u { >>>>>>> struct A a; >>>>>>> struct B b; >&gt...