This is happening in 30 minutes. Rainer will be here through the talk, and
can operate the recording equipment, so we're all good there.
I apologize for the spam for everyone not in Portland. We're going to get
the talk on air.mo, so interested folks can watch it there.
bholley
On Wed, Dec 3, 20
Hi, there,
I would like to held a session to introduce a new project, FoxEye. The goal of
this project is trying to bring modern computer vision technologies to the Web.
I would like to hear your valuable inputs.
When: 3:00 PM, Thursday, 4-Dec-2014
Where: Salon D, Ball-room level, Marriott Water
On Thu, Dec 4, 2014 at 12:35 PM, Seth Fowler wrote:
> I’d like to change the coding style guide to let us make out-params more
> obvious by using an ‘o’ prefix for their name instead of an ‘a’. For
> example,
>
> nsresult Modify(int aCount, size_t aSize, char* oResult);
>
> This will make it clea
> On 2014-12-04, at 10:51, Nicholas Nethercote wrote:
>
>> What fraction of these cases can't be distinguished by making non-out
>> ref/pointer parameters const?
>
> The non-const-ness of a parameter is a weak, indirect indication that
> it's an outparam, and one that is probably not consistent
On Thu, Dec 4, 2014 at 10:51 AM, Nicholas Nethercote wrote:
> On Fri, Dec 5, 2014 at 5:41 AM, Eric Rescorla wrote:
> >
> >> I’d like to change the coding style guide to let us make out-params more
> >> obvious by using an ‘o’ prefix for their name instead of an ‘a’. For
> >> example,
> >
> > Wha
I typically append "Out" to these parameter names. The o prefix would be more
concise. +1
Thanks!
Ben
- Original Message -
From: "Seth Fowler"
To: "dev-platform"
Sent: Thursday, December 4, 2014 1:35:06 PM
Subject: Proposal: Change the coding style guide to allow an 'o' prefix to
On Thursday 2014-12-04 10:35 -0800, Seth Fowler wrote:
> I’d like to change the coding style guide to let us make out-params more
> obvious by using an ‘o’ prefix for their name instead of an ‘a’. For example,
>
> nsresult Modify(int aCount, size_t aSize, char* oResult);
>
> This will make it cl
On Fri, Dec 5, 2014 at 5:41 AM, Eric Rescorla wrote:
>
>> I’d like to change the coding style guide to let us make out-params more
>> obvious by using an ‘o’ prefix for their name instead of an ‘a’. For
>> example,
>
> What fraction of these cases can't be distinguished by making non-out
> ref/poi
On Thu, Dec 4, 2014 at 10:35 AM, Seth Fowler wrote:
> I’d like to change the coding style guide to let us make out-params more
> obvious by using an ‘o’ prefix for their name instead of an ‘a’. For
> example,
>
> nsresult Modify(int aCount, size_t aSize, char* oResult);
>
> This will make it clea
I’d like to change the coding style guide to let us make out-params more
obvious by using an ‘o’ prefix for their name instead of an ‘a’. For example,
nsresult Modify(int aCount, size_t aSize, char* oResult);
This will make it clear just from the declaration of a function or method which
parame
[Sorry, white space got eaten up in the previous mail...]
Nicholas Nethercote wrote:
This is already present in the example at
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes:
class MyClass
: public X // when deriving from more than one class, put each on
Nicholas Nethercote wrote:
This is already present in the example at
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes:
class MyClass
: public X // when deriving from more than one class, put each on its
own line
, public Y
I have encountered far more examp
12 matches
Mail list logo
