New images up with fixes

[Bill Sun]

Oops!  There is a little typo in config.in line 34.

It is missing a space between the ifeq and the
parenthesis:

ifeq (MINGW,$(findstring MINGW, $(OS)))
    ^

-Bill

--- Brian Rice <water at tunes.org> wrote:

> And some important notes:
> 
> 1) Lee has fixed the new Debugger so that it works
> before the REPL  
> starts - this should allow easy debugging of
> bootstrap issues.
> 2) The print method has now been changed into a
> printOn: Console, and  
> all existing print-calls have been adjusted to use
> the more  
> appropriate name printString (which method already
> existed).
> 
> On Jun 7, 2005, at 8:34 PM, Brian Rice wrote:
> 
> > Okay, Windows users, the issue should be fixed!
> Grab the latest  
> > patches and images, and tell me if it breaks! :)
> >
> > On Jun 7, 2005, at 4:31 PM, Brian Rice wrote:
> >
> >
> >> New alpha images are up with various fixes as I
> found them in  
> >> surrounding libraries.
> >>
> >> I have created a new parser for filenames which
> is much more  
> >> generic and robust (and satisfies every test I've
> thrown at it -  
> >> tests/file.slate includes some examples now), but
> currently the  
> >> bootstrap which includes these is broken, so I'll
> have to continue  
> >> to work on it to get it integrated and delivered.
> Hopefully this  
> >> will be soon.
> >>
> >> In the meantime, my initial patch is in the main
> repository but  
> >> not bootstrapped in, of course. If you read it
> carefully, you will  
> >> see that it can be loaded into a live image and
> you can try it and  
> >> it should work, although more files than just
> lib/file.slate are  
> >> modified (eg the pre-bootstrap and
> directory.slate), so don't  
> >> expect a trivial load-and-go - just FYI.
> >>
> >> On Jun 7, 2005, at 11:41 AM, Brian Rice wrote:
> >>
> >>> It appears that Windows paths are not correctly
> parsed, and  
> >>> furthermore that this is the issue with
> "Directory current" being  
> >>> used in pathnames after directory.slate is
> loaded. I am working  
> >>> on the filename-parsing code to handle all of
> this robustly. A  
> >>> fix should be out in a few hours.
> >>>
> >>> Thanks, and sorry for the trouble.
> 
> --
> -Brian
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com