[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[DotGNU]OT: rant on ECMA BCL

From: S11001001
Subject: [DotGNU]OT: rant on ECMA BCL
Date: Fri, 26 Apr 2002 12:38:29 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.9+) Gecko/20020425

$BCL="ECMA CLI Base Class Library Standard"
cat << EndOfRant
So I'm writing System.IO.MemoryStream, and I have this idea about how it should be like a FIFO; eg, you read in some data at the beginning posn and write it at the end posn and it acts as a buffer, so you can send data around.

But annoying bastard BCL thinks that there should only be one posn property, and it changes when you read and changes when you write. This baffles me until I realise that they really do mean it, and you read to and write from the same posn, like a pointer that you increment or something. What was once a useful idea for a class is now totally useless.

Stephen Compall
DotGNU `Contributor' --

I see you chose the password "starfish." I suggest that you switch to
the password "carriage return." It's much easier to type, and also it
stands up to the principle that there should be no passwords.
        -- Output to a user trying to change his password on the MIT
        LCS system, part of RMS's 0-length password crusade

reply via email to

[Prev in Thread] Current Thread [Next in Thread]