I'd say that it is irrelevant in which order you write conditions in the WHERE clause, as the optimizer determines the order in which Oracle joins tables based on the join conditions, indexes on the tables, and, in the case of the cost-based optimization approach, statistics for the tables.
However: do you really have such an example? Did you try to run the same query twice, having the only difference order of the WHERE conditiions? Did you gather statistics? What did TKPROF say?
P.S. I've just found this article; it says that there is the ordered_predicates hint which is specified in the WHERE clause of a query and is used to specify the order in which Boolean predicates should be evaluated. But, in another article, I read that this hint will be (is, actually) deprecated in Oracle 10g.
I'd go with everything Littlefoot said. Never try and second guess the optimizer, try it out and see what happens. This also means you have to try it out on your production server as Oracle can alter the execution plan according to the speed and configuration of your server.