Bug 1165 : Saving sketch with the same name as a class or primitive breaks sketch
Last modified: 2010-03-22 10:35




Status:
ASSIGNED 		Resolution:
- 		Priority:
P2 		Severity:
normal

 

Reporter:
chandler 		Assigned To:
fry

Attachment Type Created Size Actions

Description:   Opened: 2009-02-18 18:23
using 1.0.1 / osx 10.5
1) make a new sketch, name it "boolean" hit run
or
2) make new sketch, name it PImage, try to load in image, hit run

in both cases you get difficult to debug errors.
Additional Comment #1 From fry 2009-02-20 11:48
That's just not something I can fix: there's not really a good stopping
point on how we police the names of sketches. I would hope that common
sense would say that you shouldn't make a class named PImage that uses a
built-in class named PImage.
Additional Comment #2 From chandler 2009-02-20 12:12
i could add a list to Sketch.checkName, if you'll accept it :) it has happened a few times in
class. Introduce a new type and someone names the sketch after that type.
Additional Comment #3 From chandler 2009-02-21 21:05
related bug, one can overwrite the libraries or tools folder. Someone could easily not know that
is a reserved directory and make a new sketch with one of those names.
Additional Comment #4 From MrFeinberg 2010-03-18 07:00
Hmm. I think you should reopen this. It doesn't sound unfixable.
This bug is now being tracked here.