|
Why dont you write your own IList object like to your queries
|
|
|
|
|
snorkie wrote: We had a senior developer
I hope for your part, the tense is correct 
xacc.ide - now with TabsToSpaces support IronScheme - 1.0 beta 1 - coming soon ((lambda (x) `((lambda (x) ,x) ',x)) '`((lambda (x) ,x) ',x))
|
|
|
|
|
Yeah, he is gone. But on the lighter side, we find all sorts of gems in our code that make us shake our heads and laugh.
Hogan
|
|
|
|
|
In that way the Senior is always with you, in both code and memory 
|
|
|
|
|
snorkie wrote: string[] results = new string[arraylist.count];
arraylist.CopyTo(results, 0);
return results;
Of course this is utterly inefficient. Everybody knows that a recursive function is always faster than a non-recursive one. So CopyTo() needs to be replaced by a recursive function! And by the way, there is nothing to stop you from writing recursive subrounties in TRS-80 BASIC!
_____________________________________
Action without thought is not action
Action without emotion is not life
|
|
|
|
|
Did you say senior  !!! my GOD 
Redwan Al-Bougha
|
|
|
|
|
Redwan Al-Bougha wrote: say senior
Yes, he did, and in a reply he mentions the senior developer is no longer with them.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
I don't know what he was smoking, an ArrayList or generic List<> simply manage a single array under the covers, resizing it as required. You need to be able to allocate a contiguous array to hold all the elements.
Maybe he was confused with C++'s deque, which does generally manage multiple array segments.
.NET has no concept of near or far heaps. It does have a Large Object Heap which is used for large allocations; the belief is that large objects will generally be kept around so the Large Object Heap is swept at the same time as a Generation 2 garbage collection. This can keep otherwise short-lifed objects around. The choice of regular or Large Object heaps is only down to the size of the objects themselves: a 1MB array or a 1MB capacity for an ArrayList makes no difference.
One distinction between ArrayList and, say, an int[] is that ArrayList manages an object[], which causes value types to be boxed when added to the collection and unboxed when they're used. In contrast the generic List<int> manages an int[], but that means an actual copy of the implementation is required, and generated by the JIT, for every different value type that is used as a type parameter. The same implementation is used for all reference types.
string is, of course, a reference type.
Arrays themselves are reference types so there should be no difference in passing an array or an ArrayList between methods. He probably managed to measure JIT time and got an incorrect answer, or simply got a page fault or a reschedule in the middle of a measurement.
It can be convenient to build something in an ArrayList then copy to an array when you don't know how big the array needs to be at the outset, and you can't change the rest of the code to use an ArrayList instead. If you wrote your own, you'd probably end up mirroring the code in ArrayList itself. Many .NET controls and methods support binding to an IList to give you some flexibility in the container you use.
"Multithreading is just one damn thing after, before, or simultaneous with another." - Andrei Alexandrescu
|
|
|
|
|
IList obviously keeped back an HTable and under the sorting algorithim it has used the QuicSort. So it can be use an ArrayList of generic or any enumeratic variations that hold the algorithm.
There many ways to develop for any special queries by an arraylist.
There have some question;;;
1- Why?
2- What is our aim
3- What is our strategy it is linking to the platform and technology
4- which is cheaper for our credentials
5- Prefere
|
|
|
|
|
I don't get why people cling to arrays in C#, they are less easy to use than egneric Lists and hvae a similary large overhead (the amount of methods available for an array is pretty much the same as for a List).
From what heard there is also no speed improvement.
And Arraylist should be used as rarely as possible, if all elements have the same type, it's easier to work ith them instead of first having to cast each object.
Besides worker threads, that only have 1 object as possible parameter, I can't think of the nedd to hae differnt bkect types in the same collection.
modified on Tuesday, February 24, 2009 9:16 AM
|
|
|
|
|
Hello,
I do not know if this is a horror or not, but it was a horror for me.
In a project i wrote this little gem:
#define stdcall_api __stdcall
Do not do that ever. Now i cannot build any project in Visual C++ (2008).
I think this is really a horror, no?
|
|
|
|
|
Dunno, does it conflict with something? If not, what's the problem?
|
|
|
|
|
Judging by the "Now i cannot build any project in Visual C++ (2008).", I'd say that's quite a horror - although I can't see how a #define could affect "any project", unless added to a (very) commonly include header.
|
|
|
|
|
Right, but it must conflict with something. And did it work in 2005?
|
|
|
|
|
Hello thoru,
Although I was sure that this issue should not make any error  . I gave it a try in my installed VS2008 in my machine.
I made a new C++ project with a precompiled headers and non-empty project, every thing went good  .
Redwan Al-Bougha
|
|
|
|
|
Maybe this isn't the right place for this post since I don't have the code (so please move it if it doesn't belong), but it is clearly a horror on the part of the original programmers.
We use the enterprise shipping software of a major shipping company (that uses yellow trucks with red lettering). Whenever we ship something using the software, a floppy disk must be in the drive (even though it neither reads a file from the disk or writes a file to the disk), otherwise it will fail with a .NET error WHILE TRYING TO EXECUTE THE C# COMPILER!
While I'm sure that in some circumstances, writing code on the fly can be beneficial, I cannot even begin to imagine that it is even remotely necessary for shipping packages.
|
|
|
|
|
What does it do if you don't have a floppy drive?
|
|
|
|
|
I don't know. The machine that they provided has one. It's just on the one machine which has the scale and label printer attached.
|
|
|
|
|
Sounds like a poor mans dongle 
xacc.ide - now with TabsToSpaces support IronScheme - 1.0 alpha 4a out now (29 May 2008) ((lambda (x) `((lambda (x) ,x) ',x)) '`((lambda (x) ,x) ',x))
|
|
|
|
|
You wouldn't want someone belittling your dongle, would you?
|
|
|
|
|
even worse, it's a poor man's floppy dongle!
|
|
|
|
|
Scott Barbour wrote: a floppy disk must be in the drive
Any floppy disk, or a specific one provided by them?
|
|
|
|
|
Scott Barbour wrote: cannot even begin to imagine that it is even remotely necessary for shipping packages.
Same here.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
I guess the message was "Drive not A not Ready" from crss.exe. The reason for that is simple.
You have in your application somewhere a drive letter selection combo box.
That little snippet should exhibit this problem:
foreach (DriveInfo d in DriveInfo.GetDrives())
{
Console.WriteLine("Root: {0}", d.RootDirectory);
}
All you have to do is to check the DriveType if it is removeable and skip it altogether. If you do not access it then you wont have any problems with drive not ready messages.
Yours,
Alois Kraus
|
|
|
|
|
I found this in some legacy code at a place where I worked:
public class MyClass
{
private FooEventArgs Foo_Event;
public void MyMethod()
{
Foo_Event = new FooEventArgs( … );
.
.
.
}
}
Foo_Event is used only in MyMethod, but it is declared as an instance variable of the class. At least they did not make it public  .
Also I really don't like having "_Event" appended to the variable name. It isn't an event it is event arguments.
Of course, this pattern was repeated for several variables.
Bill W
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
