Re: octave contributing guidelines

[Jaroslav Hajek]

On Mon, Aug 25, 2008 at 7:18 PM, Jaroslav Hajek <address@hidden> wrote:
> On Mon, Aug 25, 2008 at 10:52 AM, David Bateman
> <address@hidden> wrote:
>
>>
>> Did something like this ever make it into the manual of a released version
>> of Octave? I was looking for a coding standard document to point some one
>> too and remember this docuemnt, but can't find it in the current sources.
>>
>
> I have withdrawn that from my public repo which I needed to use for
> something other. But the chapter is written (though certainly
> incomplete), I just forgot about it. I'll try to submit a patch in a
> couple of days.
>

And here it is. I didn't make further editing (because that way I
could put it off forever), so perhaps some things may need to be
adjusted.
An instance is CamelCasing. The current state seems to be that
CamelCasing is only used for class names in the liboctave "API":
Matrix, FloatMatrix, ComplexSVD etc.
Since this sounds like a reasonable guideline, I suggest sticking to
it and formalizing it in contrib.txi.

> regards
>
>> D.
>>
>>
>> --
>> David Bateman                                address@hidden
>> Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) Parc Les
>> Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 91193
>> Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)
>> The information contained in this communication has been classified as:
>> [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola
>> Confidential Proprietary
>>
>>
>
>
>
> --
> RNDr. Jaroslav Hajek
> computing expert
> Aeronautical Research and Test Institute (VZLU)
> Prague, Czech Republic
> url: www.highegg.matfyz.cz
>



-- 
RNDr. Jaroslav Hajek
computing expert
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz

contrib.diff
Description: Text Data