Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove non functional marker persistency from network component #473

Merged
merged 1 commit into from
Aug 22, 2016

Conversation

commy2
Copy link
Contributor

@commy2 commy2 commented Aug 20, 2016

When merged this pull request will:

  • CBA_fnc_set/add/remove/getMarkerPersistent do nothing in Arma 3. All global markers are always persistent
  • No one uses these functions, so we should just nuke them.

@commy2 commy2 added this to the 3.0.1 milestone Aug 20, 2016
@jonpas
Copy link
Member

jonpas commented Aug 20, 2016

💥

@commy2 commy2 changed the title remove non functional marker persistency component remove non functional marker persistency from network component Aug 20, 2016
@Killswitch00
Copy link
Contributor

Ideally, we'd have a "stop using this function, it will be removed soon" helper macro similar to DEPRECATE. How did you determine that "no one uses these functions"?

@commy2
Copy link
Contributor Author

commy2 commented Aug 21, 2016

How did you determine that "no one uses these functions"?

All I did was a google search. At least no open source project is using it. All I could find is A2 scripts from 2010.
I really doubt that any closed project uses it either. The function never did anything in Arma 3. There was a need for this back in A2, but not anymore.

I could make DEPRECATED functions for these (at least for set and get, add and remove where already deprectaed years ago.) But all that would do is write an error message into the RPT, nothing else.
If someone actually uses these functions and we remove them, all that would happen is that a "undefined variable used" error is logged. So essentially the same thing as if we properly deprecate them.
I somehow feel that making a function just to exchange one error for another is not worth it.

@Killswitch00
Copy link
Contributor

Ok, let's ditch them.

@Killswitch00 Killswitch00 merged commit 3b63db7 into master Aug 22, 2016
@shadez95
Copy link
Contributor

if (_persist) then { [_m, true] call CBA_fnc_setMarkerPersistent };

Above is still using CBA_fnc_setMarkerPersistent

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

Successfully merging this pull request may close these issues.

4 participants