Skip to content
This repository has been archived by the owner on Jun 2, 2018. It is now read-only.

Migration to 2.0 - bk_ prefix #202

Closed
raspu opened this issue Dec 13, 2013 · 10 comments
Closed

Migration to 2.0 - bk_ prefix #202

raspu opened this issue Dec 13, 2013 · 10 comments

Comments

@raspu
Copy link

raspu commented Dec 13, 2013

Hey first thanks for this library, is awesome!

After I updated to 2.0 all the BK methods comes with the bk_ prefix, Is there any way to add an alias of the methods without the bk_ prefix like in Magical Record? Or do I need to change all my code... ?

@iliaskarim
Copy link
Contributor

ditto--I had the same question and couldn't find a solution like the one supported in Magical Record

for now I have just prefixed all BK methods with bk_

@drn
Copy link

drn commented Jan 7, 2014

+1 I added bk_s to all the BlocksKit methods calls, but it would be great to have that functionality again.

@jamescmartinez
Copy link

+1

1 similar comment
@huguesbr
Copy link
Contributor

+1

@julasamer
Copy link

+1 At least, some reasoning why you introduced the prefix would be nice.

@zwaldowski
Copy link
Collaborator

+1

It's not happening.

why you introduced the prefix

It's the right thing to do.

It's not difficult, guys. I'm sorry I caused an inconvenience, but it's the right thing to do.

@huguesbr
Copy link
Contributor

I think the point is not really to remove the prefix but to allow to define a constants to disable it. Prefixing is unfortunately require in the objective-c world, but not necessary if you know your library in which case you can disable it...

@zwaldowski
Copy link
Collaborator

I understand the point. It's not happening. Believe it or not, there are users of this library that are less attentive than you and I have better things to do with my time than provide support for issues with namespace collisions. I have witnessed firsthand a project with several block convenience libraries, all including a -map: that jump all over one another. I will contribute to these issues no longer. If we ever get namespacing or library symbol relocation, I will be proactively (and will happily) ditch the prefixes.

@iliaskarim
Copy link
Contributor

hey Zach,

great point. thanks for taking the time to respond and explain your decision! I completely understand.

On Mar 11, 2014, at 1:25 PM, Zachary Waldowski [email protected] wrote:

I understand the point. It's not happening. Believe it or not, there are users of this library that are less attentive than you and I have better things to do with my time than provide support for issues with namespace collisions. I have witnessed firsthand a project with several block convenience libraries, all including a -map: that jump all over one another. I will contribute to these issues no longer. If we ever get namespacing or library symbol relocation, I will be proactively (and will happily) ditch the prefixes.


Reply to this email directly or view it on GitHub.

@raspu
Copy link
Author

raspu commented Mar 12, 2014

Understood, it's a valid decision, thanks for taking the time to explain this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants