Re: Question about structs and enum placement in a project
Re: Question about structs and enum placement in a project
- Subject: Re: Question about structs and enum placement in a project
- From: Igor Ranieri Elland <email@hidden>
- Date: Thu, 13 Jul 2017 15:56:01 +0200
If they’re not being declared inside another object, why not put them in their
own files?
> Am 13.07.2017 um 15:53 schrieb Eric E. Dolecki <email@hidden>:
>
> Perhaps. Then maybe a folder of categorized structs and enums? I personally
> dislike seeing them sprinkled throughout AppDelegate & other classes. It's
> easy to cntrl-click to where they are defined, but it seems like a lot of
> clutter.
>
> On Thu, Jul 13, 2017 at 9:52 AM Charles Srstka <email@hidden>
> wrote:
>
>> For a project of any appreciable size, that’s gonna be one huge file…
>>
>> Charles
>>
>>> On Jul 13, 2017, at 8:37 AM, Eric E. Dolecki <email@hidden> wrote:
>>>
>>> I am planning on putting all my structs and enums into it's own swift
>> file
>>> - to keep my project cleaner. Seems safe enough, thoughts on this?
>>>
>>> Thanks,
>>> Eric
>>> _______________________________________________
>>>
>>> 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
>>
>>
> _______________________________________________
>
> 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
_______________________________________________
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