开云体育

Box behind the CPU ? A physical one? A dialog box? CPU==IDE?
And no that is not what I know boxing and unboxing to be(value types vs
objects)

So I am lost

Can you make a video of how you work?

On Saturday, June 23, 2012, Kay A Pentecost wrote:

**

Hey, Chet,

Since I get a *lot* of compiler errors, I've placed a small box behind the
CPU to catch them. The regular errors go in there, too. I've found the
small amount of dust that also accumulates can be easily blown away. Once
the box is filled, I blow away any dust, and empty the box into the CPU.

I haven't found that the recycled errors mix themselves up at all. I don't
see code errors popping up as system errors or compiler errors as code
errors; they recycle like stem cells.

I'm working in C# now. I believe this is called "boxing and unboxing," but
I call it Digital Error Environment Process (DEEP). I'm thinking of adding
the term "System Handling Integral Technique" to it, and I'm working on a
white paper.

I happily give you (and the list members) permission to use this technique
in the beta form, as long as you credit me and use the correct terminology
so everyone will think I'm more brilliant and creative than I actually am.

I've learned all this from the work I've done with VSIPC.

Kay Pentecost