EVGD: Códigos Toscos

GUJ Expert Membro desde: 18/02/2008 16:17:53 Mensagens: 3002 Offline

Eu tinha um colega que quando fazia um booble-sort com objetos do tipo Pessoa, colocava o nome da variável temporária de jesus. O motivo: "Apenas Jesus pode salvar as Pessoas".

...

Enquanto isso, na classe utilitária do sistema:

// guaranteed to hold execution of current thread for at least the specified number of milliseconds
  public static void hold(int millis) {
    int remainder = millis;
    long start = System.currentTimeMillis();
    do {
      try {
        Thread.sleep(Math.max(MIN_PAUSE_INTERVAL,  remainder));
      } catch (InterruptedException _) { }
      remainder = millis - (int)(System.currentTimeMillis() - start);
    } while (remainder > 0);
  }
  
  // return 'true' if the the specified number of milliseconds has elapsed
  public static boolean sleep(int millis) {
    long start = System.currentTimeMillis();
    try {
      Thread.sleep(Math.max(MIN_PAUSE_INTERVAL, millis));
    }
    catch (InterruptedException _) { }
    return (millis <= (int)(System.currentTimeMillis() - start));
  }

// wait until one of the following takes place:
  //   - the provided monitor is signalled
  //   - a spurios wakeup has occurred
  //   - the specified number of milliseconds has elapsed
  // return 'true' if the the specified number of milliseconds has elapsed
  public static boolean wait(Object monitor, int millis) {
    int remainder = millis;
    long start = System.currentTimeMillis();
    synchronized (monitor) {
      do {
        try {
          monitor.wait(Math.max(remainder, MIN_PAUSE_INTERVAL));
          remainder = millis - (int)(System.currentTimeMillis() - start);
          break;
        } catch (InterruptedException e) {
          remainder = millis - (int)(System.currentTimeMillis() - start);
        }
      } while (remainder > 0);
    }
    return (remainder <= 0);
  }

// wait until one of the following takes place:
  //   - the provided callable monitor returns 'true' upon inquiry
  //   - the specified number of milliseconds has elapsed
  // return the monitor's response to the last inquiry
  public static boolean wait(Callable<Boolean> monitor, int millis) throws IllegalStateException {
    boolean result;
    try {
      result = monitor.call().booleanValue();
    } catch (Exception e) {
      throw new IllegalStateException(e);
    }
    if (!result) {
      int remainder = millis;
      long start = System.currentTimeMillis();
      synchronized (monitor) {
        do {
          try {
            monitor.wait(Math.max(remainder, MIN_PAUSE_INTERVAL));
            try {
              result = monitor.call().booleanValue();
            } catch (Exception e) {
              throw new IllegalStateException(e);
            }
          } catch (InterruptedException _) { }
          remainder = millis - (int)(System.currentTimeMillis() - start);
        } while (!result && remainder > 0);
      }
    }
    return result;
  }

Lindo!!!!!!!!!

Um dos "famosos" truques para apresentar a tela de "Aguarde, carregando...", para impressionar o usuário com uma Splash Screen bonita. rsrsrs

Nome da classe: CobrancaWebServiceDelegateServiceLocator

Isso é o que eu chamo de multi-pattern!

O if...else que eu nem acreditei quando vi:

Olha, vou dizer que tem programador que tem o "dom" de fazer isso funcionar.. hahahahaha

This message was edited 1 time. Last update was at 10/11/2009 14:28:56

Super-jeito-bom-de-tratar-exceção:

"Super-bom" comparar as mensagens i18n da exceção para ver o "tipo" do erro, ainda mais com HTML incluso. Acho que neste caso um código ajudaria.

GUJ Expert Membro desde: 10/07/2006 10:37:23 Mensagens: 3161 Offline

ozix wrote: public boolean isEmpty() { return ((lista == null) && (lista.size() != 0)); }

esse ai logo logo vai receber um belo de um NullPointerException

Moderador Membro desde: 23/12/2006 21:05:04 Mensagens: 3083 Offline

Oi,

Revirando a codificação da sun:

/**
     * Provides a hint as to whether or not newly created <code>JDialog</code>s
     * should have their Window decorations (such as borders, widgets to
     * close the window, title...) provided by the current look
     * and feel. If <code>defaultLookAndFeelDecorated</code> is true,
     * the current <code>LookAndFeel</code> supports providing window
     * decorations, and the current window manager supports undecorated
     * windows, then newly created <code>JDialog</code>s will have their
     * Window decorations provided by the current <code>LookAndFeel</code>.
     * Otherwise, newly created <code>JDialog</code>s will have their
     * Window decorations provided by the current window manager.
     * <p>
     * You can get the same effect on a single JDialog by doing the following:
     * <pre>
     *    JDialog dialog = new JDialog();
     *    dialog.setUndecorated(true);
     *    dialog.getRootPane().setWindowDecorationStyle(JRootPane.PLAIN_DIALOG);
     * </pre>
     *
     * @param defaultLookAndFeelDecorated A hint as to whether or not current
     *        look and feel should provide window decorations
     * @see javax.swing.LookAndFeel#getSupportsWindowDecorations
     * @since 1.4
     */
    public static void setDefaultLookAndFeelDecorated(boolean defaultLookAndFeelDecorated) {
        if (defaultLookAndFeelDecorated) {
            SwingUtilities.appContextPut(defaultLookAndFeelDecoratedKey, Boolean.TRUE);
        } else {
            SwingUtilities.appContextPut(defaultLookAndFeelDecoratedKey, Boolean.FALSE);
        }
    }

Tchauzin!

ps:. tinha exatamente esse coment..."não faz nada"
acho q n conhecia o "!condicao"

não é código, mas continua tosco:

danieldestro wrote:Nome da classe: CobrancaWebServiceDelegateServiceLocator

Isso é o que eu chamo de multi-pattern!

q nada é híbrido!

JWizard Membro desde: 23/02/2007 15:52:55 Mensagens: 2034 Offline

Notícias, artigos e o maior fórum brasileiro sobre Java