[go-nuts] Is there any reason to NOT name a package with captital letters?

On 2 February 2014 15:35, Hotei wrote:

I note that the VAST majority of packages (on godoc.org for example)
begin with a lowercase letter. However the language and implementation
allows uppercase package names. Is there any downside to using an
uppercase pkg name? I've only got a few with leading uppercase, but one of
them I use frequently and I don't want to get too far downstream and find
there's a subtle problem with that choice.

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On 3 Feb 2014, at 1:42, Andrew Gerrand wrote:

No technical reason that I'm aware of, but it does defy convention. That harms readability.

Andrew

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Sun, Feb 2, 2014 at 7:51 PM, Dave Cheney wrote:
Mixed case causes all sorts of issues on windows and OSX. On those systems
Package and package refer to the same thing.

On Sunday, February 2, 2014 9:35:05 AM UTC-5, Hotei wrote:

I note that the VAST majority of packages (on godoc.org for example)
begin with a lowercase letter. However the language and implementation
allows uppercase package names. Is there any downside to using an
uppercase pkg name? I've only got a few with leading uppercase, but one of
them I use frequently and I don't want to get too far downstream and find
there's a subtle problem with that choice.

Thanks in advance.

On Sun, Feb 2, 2014 at 6:54 PM, Hotei wrote:

Seeking clarity on this - would a camelCase package name cause the same
issues? Sounds like it would, but I both camel and upper named packages in
a mixed go environment (65% Linux, 30% FreeBSD, 5% Windows7) and have yet
to run into any problems. Several of my utility package names are
camelCase and the most frequently used one is upper only. I'm changing
them to increase interoperability, but it it's this big an issue maybe go
vet needs to bark about it? Since it's legal (spec-wise) that may be about
all one can hope for.

I'm also assuming this conventional proscription on mixed case also
applies to the import path as well as the package name.


--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Mon, Feb 3, 2014 at 1:54 PM, Hotei wrote:

Seeking clarity on this - would a camelCase package name cause the same
issues? Sounds like it would, but I both camel and upper named packages in
a mixed go environment (65% Linux, 30% FreeBSD, 5% Windows7) and have yet
to run into any problems. Several of my utility package names are
camelCase and the most frequently used one is upper only. I'm changing
them to increase interoperability, but it it's this big an issue maybe go
vet needs to bark about it? Since it's legal (spec-wise) that may be about
all one can hope for.

I'm also assuming this conventional proscription on mixed case also
applies to the import path as well as the package name.


--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Sunday, February 2, 2014 9:35:05 PM UTC+7, Hotei wrote:

I note that the VAST majority of packages (on godoc.org for example)
begin with a lowercase letter. However the language and implementation
allows uppercase package names. Is there any downside to using an
uppercase pkg name? I've only got a few with leading uppercase, but one of
them I use frequently and I don't want to get too far downstream and find
there's a subtle problem with that choice.

Thanks in advance.