Bug 65880 - Cheetah enhanced-for crashes on cut/copy
Summary: Cheetah enhanced-for crashes on cut/copy
Status: RESOLVED DUPLICATE of bug 59052
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows All
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-05 18:18 EDT by Alan Malloy CLA
Modified: 2004-06-06 10:21 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Malloy CLA 2004-06-05 18:18:30 EDT
Overview:
  Java files with an enhanced for loop in them cause entire-program crash (or 
occasionally just an error message) when attempting to copy or cut to the 
system clipboard.

Reproduce:
  1) Make sure the version of Eclipse you're using has Cheetah plugged in
  2) Create a simple Java class, with an enhanced for loop in it, such as:
     int[] array = new int[5];
     for (int a : array)
       System.out.println(a);
  3) Highlight ANY part of the file and attempt to copy it to the system 
clipboard.

Actual results:
  One of two things may happen - I can't figure out what causes which to happen.
  1) Entire Eclipse program ceases to respond and must be shut down from the 
Windows Task Manager
  2) Error message window pops up but Eclipse continues to function.
     Error message follows below:
Error window title: "Error executing command"
Error window text:
"
The command for the key you pressed failed

Reason:
  Not yet implemented: convert(class 
org.eclipse.jdt.internal.compiler.ast.ForeachStatement)
"

Expected results:
  The selected text should be copied to the system clipboard, and Eclipse 
should otherwise behave as if nothing has happened.

Build and platform:
  Eclipse 3.0M9, with Cheetah early-access plug-in installed, Windows 98SE
  - Also occurs on Windows XP Home edition.
Comment 1 Olivier Thomann CLA 2004-06-06 10:21:34 EDT

*** This bug has been marked as a duplicate of 59052 ***