• 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: Need for Swift
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need for Swift


  • Subject: Re: Need for Swift
  • From: Jens Alfke via Cocoa-dev <email@hidden>
  • Date: Tue, 15 Oct 2019 16:32:59 -0700


> On Oct 15, 2019, at 10:52 AM, Turtle Creek Software <email@hidden>
> wrote:
>
> Diving down into C sounds like a reasonable option for a database library.
> It does not sound good for a specialty app that does construction estimating
> and accounting.

I don't see the difference, for the purposes of this discussion. Either way
you'd have core code in C++ that you call into via a C API.

> Libraries just show Assembly when you step into them, no?

No. Not if it's a static library; and not if it's a dynamic library you have
symbols for, as you do if you built it.

—Jens
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Need for Swift (From: Turtle Creek Software via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Richard Charles via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Jens Alfke via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Turtle Creek Software via Cocoa-dev <email@hidden>)

  • Prev by Date: Re: Need for Swift
  • Next by Date: Re: Need for Swift
  • Previous by thread: Re: Need for Swift
  • Next by thread: Re: Need for Swift
  • Index(es):
    • Date
    • Thread