Uso de this->

[ivanpondal]

Vi que se usa en algunos pero no todos los casos en los que se accede a la parte privada, esto como nice to have estaría bueno decidirse por uno u otro

[franciscod]

si, yo estoy acostumbrado a ponerlo siempre, creo que es porque vengo del palo de C.

es mucho mas limpio no ponerlo. lo volamos?

[ivanpondal]

yo no me opongo a tenerlo! pero si lo ponemos que sea en todos lados. Por mi pongamoslo

[franciscod]

en el codigo que nos dieron no estaba, propongo sacarlo :p

[franciscod]

ah no, ese codigo lo hiciste vos jajajaj... googleemos al respecto

[franciscod]

segun el zen de python 'Explicit is better than implicit' así que pongamoslos :D (?)

% python
Python 3.4.3 (default, Mar 25 2015, 17:13:50) 
[GCC 4.9.2 20150304 (prerelease)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
>>> 

[ivanpondal]

JAJAJAJA justo python viene a hablar de cosas explícitas??? está bien que no es groovy pero...

[franciscod]

creo que es más abstracto, en el sentido de que haya la menor magia posible

[ivanpondal]

sisi, me encantó la filosofía!