[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Audio playback and classes
From: |
Jordi Gutiérrez Hermoso |
Subject: |
Re: Audio playback and classes |
Date: |
Wed, 19 Jun 2013 12:55:58 -0400 |
On 19 June 2013 12:40, Vytautas Jancauskas <address@hidden> wrote:
>>> You will need a get and set method defined in a @audioplayer directory, but
>>> they can be simple wrappers around some internal functions, which can then
>>> exist anywhere in octave path (even as an autoloaded function).
>>
>> This is exactly what happens with the ftp class. See scripts/@ftp,
>> these functions are pretty much 1 liners, wrappers to the __ftp_*.
>>
>> Carnë
>
> What is a good naming convention for these low level functions that
> will get wrapped by octave class methods? I see @ftp adds two
> underscores in front.
We use two underscores both front and back for functions that are
supposed to be internal and not called by the user.
We don't universally uphold this convention, but we should.
- Jordi G. H.
- Audio playback and classes, Vytautas Jancauskas, 2013/06/17
- Re: Audio playback and classes, Michael Goffioul, 2013/06/17
- Re: Audio playback and classes, Jordi Gutiérrez Hermoso, 2013/06/18
- Re: Audio playback and classes, Mike Miller, 2013/06/18
- Re: Audio playback and classes, Michael Goffioul, 2013/06/18
- Re: Audio playback and classes, Carnë Draug, 2013/06/18
- Re: Audio playback and classes, Vytautas Jancauskas, 2013/06/19
- Re: Audio playback and classes,
Jordi Gutiérrez Hermoso <=
- Re: Audio playback and classes, Mike Miller, 2013/06/21
- Re: Audio playback and classes, Vytautas Jancauskas, 2013/06/28
- Re: Audio playback and classes, Michael Goffioul, 2013/06/28
- Re: Audio playback and classes, Mike Miller, 2013/06/28