• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re:Bad Assembly Code Generation?[solved]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re:Bad Assembly Code Generation?[solved]


  • Subject: Re:Bad Assembly Code Generation?[solved]
  • From: Joe Osborn <email@hidden>
  • Date: Sun, 1 Sep 2002 00:50:44 -0500

Let me first say that I am a fool.

Let me second say that I really, really wish objective-c were a typeless language. Those two sentences out of the way...

GCC was incapable of generating proper assembly code because i didn't declare the methods, which took and returned c data types, in my @interfaces. So it assumed objects were involved(but wouldn't something like that(that being [self setBar:[self bar]+1]; throw an 'invalid operand to binary +' or some such? ah well). Anyway, it's all working just hunky-dory now.

I'm going to go off and be embarrassed for a while.

but hey, at least it works now.

--joie
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Bad Assembly Code Generation?[solved]
      • From: Kyle Moffett <email@hidden>
  • Prev by Date: Re: cocoa-dev digest, Vol 2 #1183 - 18 msgs
  • Next by Date: Re: AppKit now thread-safe?
  • Previous by thread: Re: cocoa-dev digest, Vol 2 #1183 - 18 msgs
  • Next by thread: Re: Bad Assembly Code Generation?[solved]
  • Index(es):
    • Date
    • Thread