On 02/27/2011 05:55 PM, Alexandre Julliard wrote:
The other reason is that a decent documentation of the Windows API would
be huge; look at how much information there is on MSDN, and that's still
incomplete. It's completely impossible to maintain something of that
size in the middle of the sourc
On 2 March 2011 00:32, Max TenEyck Woodbury wrote:
> First, it is _not_ a new approach. It has literally decades of
> application. I first encountered it in the '80s and it was well
> entrenched even then. Such people as D. Knuth have much to say on the
> subject.
I don't think anyone is arguing
On 02/28/2011 11:34 AM, André Hentschel wrote:
Am 28.02.2011 17:20, schrieb Max TenEyck Woodbury:
I think the idea of building upon the existing "documentation" somewhere else
has a better chance than the "deal on the 100"
Frankly, I believe embedded documentation is the way to go. It is _not_
Max TenEyck Woodbury writes:
> Frankly, I believe embedded documentation is the way to go. It is _not_
> a panacea, but it is better than trying to maintain a separate set of
> functional documentation. I have seen cases where it worked. Not great
> but OK. I tried the separate document approach
Am 28.02.2011 17:20, schrieb Max TenEyck Woodbury:
>> I think the idea of building upon the existing "documentation" somewhere else
>> has a better chance than the "deal on the 100"
>>
> Frankly, I believe embedded documentation is the way to go. It is _not_
> a panacea, but it is better than tryin
On 02/28/2011 08:08 AM, André Hentschel wrote:
Am 27.02.2011 20:37, schrieb Max TenEyck Woodbury:
I've picked up Perl in the last couple weeks. An interesting language
with lots of adopted features. It's been easy to learn, so I think I
will _not_ need help with the language itself, but I will l
Am 27.02.2011 20:37, schrieb Max TenEyck Woodbury:
> I've picked up Perl in the last couple weeks. An interesting language
> with lots of adopted features. It's been easy to learn, so I think I
> will _not_ need help with the language itself, but I will listen to any
> advice.
When i started with
On 02/27/2011 05:55 PM, Alexandre Julliard wrote:
... If you want to prove me wrong, start writing it. Once you
have properly documented 100 functions, we can discuss what
extra infrastructure is needed for the remaining 50,000.
Deal on the 100!
Max
Max TenEyck Woodbury writes:
> I'd also like clarification on why you think it does _not_ belong in
> the source code. Some projects insist that documentation _has_ to be
> part of the source code so that it will be properly maintained.
That's because in most projects the API is defined by the
i
On 02/27/2011 02:49 PM, Alexandre Julliard wrote:
Max TenEyck Woodbury writes:
P.S. to AJ et al.
There is a _lot_ of documentation embedded in the wine code, but it is
hard to find at the moment. I'd like to see it indexed and this is the
program that does the extraction and indexing. Advice
Max TenEyck Woodbury writes:
> P.S. to AJ et al.
>
> There is a _lot_ of documentation embedded in the wine code, but it is
> hard to find at the moment. I'd like to see it indexed and this is the
> program that does the extraction and indexing. Advice on making this
> new version available and a
As my previous efforts have probably informed you, I am interested in
documentation. My initial efforts were _not_ on target and had missed
the existing 'c2man.pl' tool. I am in the process of correcting my
failure on that.
I've picked up Perl in the last couple weeks. An interesting language
wit
12 matches
Mail list logo
