On 01 Mar 2014, at 00:17, Esteban A. Maringolo <[email protected]> wrote:
> 2014-02-28 18:26 GMT-03:00 Chris Cunningham <[email protected]>: >> On Fri, Feb 28, 2014 at 6:07 AM, Esteban A. Maringolo <[email protected]> >> wrote: >>> >>> I have a naive question... >>> >>> Why if the BasicCodeLoader handler looks for .st files does the >>> Workpace offer .ws as the default extension? >> >> Well, the workspace doesn't just use chuck format - in fact, you rarely put >> in chunk format into a workspace (or do you? I certainly don't). Also, >> workspaces allow for dynamic local variables - which normal chunk loaders >> don't. The two things behave differently. .st is explicitly for runnable >> code - workspaces are for more than just code - more of a scratch pad. > > I know, but the cmd line handler isn't a chunk reader. It compiles the > content of the file and evaluate it all at once. And explicitly > expects for files with .st extension (I don't understand such > restriction). > > I don't put chunk in a workspace either (actually I don't know how to > properly read a chunk file in Pharo). > > tl;dr Frankly I don't like the .ws extension at all. It's a matter of habit. > :) > > Regards! send a fix. For me saving workspace in file looks prehistorical age. just having method to manage code snippets is much more efficient > > > > Esteban A. Maringolo >
