On Sun, Apr 26, 2020 at 7:45 AM Sven Schreiber <svetosch(a)gmx.net> wrote:
Am 25.04.2020 um 21:24 schrieb Cottrell, Allin:
> On Sat, Apr 25, 2020 at 11:57 AM Sven Schreiber <svetosch(a)gmx.net> wrote:
>>
>> I agree some convention might be good, to an extent. But we already have
>> a loose de-facto standard that you can see when looking at the list of
>> gretl functions: No CamelCase, no underscores, nothing too long,
>> uppercase only when it's an acronym (although it's actually
inconsistent
>> then to have kpsscrit, bkfilt, bkw, ghk ...).
>
> Consistency is good, and maybe trumps other considerations. But I
> think function packages are/should be allowed latitude relative to
> built-in functions. There are no underscores in names of built-ins (I
> think) but they seem fine to me for readability in function packages.
Well, the thing with 'extra' is that it is supposed to be a collections
of things that might become a built-in at some point. At least that was
my understanding.
Ok, good point.
In that sense the naming convention of builtins should be kept in
mind
at least for those functions that are performance-critical and therefore
might move to core-C-gretl. It would seem to me that MultiEqDraw or what
it's called might belong to that category. Others do not.
From that perspective, multidraw() might be good.
Allin