On 30 January 2013 13:03, Esteban Lorenzano <estebanlm@gmail.com> wrote:
makes *you* less thinking :) I think in pharo, people are used to camel case. And if we use camel case, we can always use "-" for subgroups if needed (like categories, monticello packages, etc., now)
but Nativeboost name is single word, i don't remember when i had idea of naming it like that, but i was never writing it with two separate words.. hence writing camelcase "NativeBoost" will lead people to thinking that actual project name is "Native boost" because identifiers do not allow spaces and so, you write "NativeBoost". But that's not the case.
Esteban
On Jan 30, 2013, at 12:54 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 30 January 2013 12:48, Esteban Lorenzano <estebanlm@gmail.com> wrote:
yep... Camillo already messed it by using C naming convention and not smalltalkish :P
CamelCase, please!
i prefer all lowcase bro. makes less thinking about which rules to follow.
Esteban
On Jan 30, 2013, at 12:32 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Good! can you sync with esteban for the shape of the pharo repo?
I was thinking about
Pharo /NativeBoost /RB /Opal /
so that we have a bit but not to much structure and each subproject is one that can be loaded "independently" what do you think?
Sef
On Jan 30, 2013, at 5:58 AM, Igor Stasenko wrote:
On 29 January 2013 19:45, Ciprian Teodorov <ciprian.teodorov@gmail.com> wrote:
Hi Igor,
I guess that I am a persona non-grata, or something... I've lost again my commit rights on squeaksource... ;) I have a fix for the tests on struct and unions so that they pass on mac and linux
I will migrate project on smalltalkhub in closest days. I don't wanna waste time on squeaksource anymore. I will inform you (and all) about the event.
Cheers,
-- Dr. Ciprian TEODOROV Ingénieur Développement CAO
tél : 06 08 54 73 48 mail : ciprian.teodorov@gmail.com www.teodorov.ro
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.