Memo to developers at Microsoft: when you are working on a structure
that will be released to the general public and used by developers
around the world, USE A DICTIONARY.
Second memo: there is no shame in correcting a spelling error in the
next release of the DDK. Yes, you force developers to change their
code, but you are forcing them to change it to the CORRECT spelling.
From DDK include file bdamedia.h:
typedef struct tagBDA_TRANSPORT_INFO {
ULONG ulcbPhyiscalPacket;
ULONG ulcbPhyiscalFrame;
ULONG ulcbPhyiscalFrameAlignment;
REFERENCE_TIME AvgTimePerFrame;
} BDA_TRANSPORT_INFO, *PBDA_TRANSPORT_INFO;
Few things irritate me more than having to type a misspelled word in my
OWN code, just because someone created an include file incorrectly.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Tim Roberts wrote:
…
From DDK include file bdamedia.h:
typedef struct tagBDA_TRANSPORT_INFO {
ULONG ulcbPhyiscalPacket;
ULONG ulcbPhyiscalFrame;
ULONG ulcbPhyiscalFrameAlignment;
REFERENCE_TIME AvgTimePerFrame;
} BDA_TRANSPORT_INFO, *PBDA_TRANSPORT_INFO;
Few things irritate me more than having to type a misspelled word in my
OWN code, just because someone created an include file incorrectly.
LOL… And I thought DO_POWER_PAGABLE was about as bad as it got 
Peter
OSR
What a fantastic idea for a Hall of Shame
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> Memo to developers at Microsoft: when you are working on a structure that
> will be released to the general public and used by developers around the
> world, USE A DICTIONARY.
>
> Second memo: there is no shame in correcting a spelling error in the next
> release of the DDK. Yes, you force developers to change their code, but
> you are forcing them to change it to the CORRECT spelling.
>
> From DDK include file bdamedia.h:
>
> typedef struct tagBDA_TRANSPORT_INFO {
> ULONG ulcbPhyiscalPacket;
> ULONG ulcbPhyiscalFrame;
> ULONG ulcbPhyiscalFrameAlignment;
> REFERENCE_TIME AvgTimePerFrame;
> } BDA_TRANSPORT_INFO, *PBDA_TRANSPORT_INFO;
>
> Few things irritate me more than having to type a misspelled word in my
> OWN code, just because someone created an include file incorrectly.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
I agree. But you only have to type it once (or cut and paste the one I
prepared earlier)
#define ulcbPhysicalPacket ulcbPhyiscalPacket
#define ulcbPhysicalFrame ulcbPhyiscalFrame
#define ulcbPhysicalFrameAlignment ulcbPhyiscalFrameAlignment
Don
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: 27 May 2005 22:17
To: Windows System Software Devs Interest List
Subject: [ntdev] Spelling
Memo to developers at Microsoft: when you are working on a structure
that will be released to the general public and used by developers
around the world, USE A DICTIONARY.
Second memo: there is no shame in correcting a spelling error in the
next release of the DDK. Yes, you force developers to change their
code, but you are forcing them to change it to the CORRECT spelling.
From DDK include file bdamedia.h:
typedef struct tagBDA_TRANSPORT_INFO {
ULONG ulcbPhyiscalPacket;
ULONG ulcbPhyiscalFrame;
ULONG ulcbPhyiscalFrameAlignment;
REFERENCE_TIME AvgTimePerFrame;
} BDA_TRANSPORT_INFO, *PBDA_TRANSPORT_INFO;
Few things irritate me more than having to type a misspelled
word in my
OWN code, just because someone created an include file incorrectly.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@careful.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com