From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Module Namespaces
Date: Thu, 18 Nov 2010 22:59:00 +0100 [thread overview]
Message-ID: <AANLkTimvafDHAtBvUGRu04KgHWWWCxZesPuH6C5jGvz9@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1011181647160.10790@ybpnyubfg.ybpnyqbznva>
On Thu, Nov 18, 2010 at 10:48 PM, Aditya Mahajan <adityam@umich.edu> wrote:
> On Thu, 18 Nov 2010, Hans Hagen wrote:
>
>> On 18-11-2010 10:19, luigi scarso wrote:
>>>
>>> On Thu, Nov 18, 2010 at 10:03 PM, Aditya Mahajan<adityam@umich.edu>
>>> wrote:
>>>>
>>>> On Thu, 18 Nov 2010, Wolfgang Schuster wrote:
>>>>
>>>>> (there is no need to use capitals).
>>>>
>>>> Thanks. Old habits die hard.
>>>
>>> Camel case is not bad at all --- it's a matter of points of view
>>
>> best use lowercase systematically
>>
>> then users can use uppercase or a mix and not clash with built in names
>
> As a module writer, it is not always clear whether you should follow the
> conventions for a user (use upper or mixed case to avoid clash) or a
> developer (use lowercase systematically).
Because really there is no difference between "user" and "developer"
That what I think:
lower case name are for files in base
All others should use a distinct "namespace" (ie lscarso , amahajan
etc or Filters )
--
luigi
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-11-18 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 9:13 luigi scarso
2010-11-18 9:26 ` Philipp Gesang
2010-11-18 18:08 ` Wolfgang Schuster
2010-11-18 18:33 ` luigi scarso
2010-11-29 18:17 ` Wolfgang Schuster
2010-11-29 18:52 ` Philipp Gesang
2010-11-29 19:10 ` luigi scarso
2010-12-06 16:50 ` Hans Hagen
2010-12-08 13:17 ` Philipp Gesang
2010-12-06 16:48 ` Hans Hagen
2010-11-29 18:19 ` Wolfgang Schuster
2010-11-18 21:03 ` Aditya Mahajan
2010-11-18 21:19 ` luigi scarso
2010-11-18 21:45 ` Hans Hagen
2010-11-18 21:48 ` Aditya Mahajan
2010-11-18 21:52 ` Hans Hagen
2010-11-18 21:59 ` luigi scarso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimvafDHAtBvUGRu04KgHWWWCxZesPuH6C5jGvz9@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).