Re: Bug in Windows Installer (1.4.0.3)

   I just installed Scala 1.4.0.4 in another windows machine and got
the same problem. I used the automatic installer, added
%SCALA_HOME%\bin to the path, I can get scalac -version to print the
correct version, but when I try to compile anything I get the same
errors. This is the third windows installation I do, all with the same
problem. I noticed the solution looking in gmane for the list
archives, when someone else complained about the same problem. I
thought it could be some installation option, but there are none, you
just press "Next" when asked.

   In all machines I tested the SO was Windows XP Brazilian Portuguese
edition (with and without SP2), with JDK 1.5 Update 06. Installed
scala to the %PROGRAM_FILES% directory.

--
[]s, Andrei Formiga

On 1/13/06, Stéphane Micheloud <stephane.micheloud <at> epfl.ch> wrote:
> Hi Andrei,
>
>
> I could not reproduce your problem.
>
> Here are the steps I followed:
>
> 1) Installed the Scala distribution in the directory C:\Temp\ using
>     install.exe (7'503'891 bytes) for Scala 1.4.0.3
>
> 2) In the DOS console:
>

Sbaz reference manual

I've posted a reference manual for Scala Bazaars.

        http://lamp.epfl.ch/~spoon/sbaz/

This is a place to document decisions about the system as they
accumulate.

Regards,

-Lex

Scala Eclipse Plugin Beta

Hi,

I'm happy to announce that our Scala Eclipse Plugin (2.1.0) is ready  
for public beta testing.

The remote Eclipse update site from where the plugin beta can be  
installed is located at http://lamp.epfl.ch/~mcdirmid/scala-plugin.  
Installation is standard for an eclipse plugin: activate the Help/ 
Software Updates/Find and Install.../ menu, select the "Search for  
new features to install" option, add a "New Remote Site" with the URL  
http://lamp.epfl.ch/~mcdirmid/scala-plugin and whatever name you want  
to give it, check this new update site, hit next, check the only  
feature on this site, say yes to the license, ...., restart Eclipse.  
The Scala Eclipse plugin is completely self contained, and no other  
downloads or installation steps are required. Conversely, there is no  
way to get the Scala plugin to use a pre-existing Scala distribution.

IMPORTANT: the plugin currently works under  Eclipse 3.2M4 with Java  
1.5+. Any other Eclipse/Java configuration will not work at all.  
Although platform/architecture should work, we have only tested under  
X86 Linux, Windows XP, and Mac OS X.

After you have installed the plugin and restarted Eclipse, you can  
activate the "Help/Help Contents" menu to look at the (very  
incomplete) Scala Development Tool documentation. The only  
documentation pages currently available is a "Getting Started" page  
and an "Issues" page. The getting started page will explain how to  
use the plugin to create and develop a Scala project. The "Issues"  
page lists known issues that exist in the plugin. Please take a look  
at both pages before reporting bugs.

New linearization

Been playing a bit with the new mixin classes; see 

http://scala.sygneca.com/code/shared-objects

Scala2 forces the first class "extension" to be an "extends" clause, and
does not allow "with".  This seems a bit draconian -- can an "extends
ScalaObject" not be implicitly inserted?  

The Scala2 change doc tells us that "abstract override", when used in a
mixin class that is mixed in with "with", shifts super to be the prior
definition within the class being mixed into.  

In my example I have a "FixedHash" mixin that uses abstract override to
redefine how hashes are computed.  I also have a "SharedObject" that
further refines how equality tests are done.  If I want to combine them,
the most natural thing to write is (possibly):

Mixin class FixedShared extends FixedHash with SharedObject

But I can't...because the abstract overrides on FixedHash are no longer
used.  I could do this:

Mixin class FixedShared with FixedHash with SharedObject

But that compiler won't accept that. I also cannot write:

Mixin class FixedShared extends ScalaObject with FixedHash with
SharedObject

As the compiler tells me ScalaObject is inherited twice.  I can write:

Implicit parameters

Consider:

def log(msg: String)(implicit title: String) = 
  Console.println("Log: " + title + '|' + msg);
def log(msg: String): unit = log(msg)("Default");

implicit val title = "Title";
log("Some message");
log("Another message")("Direct Title");

Scala doesn't currently have default values for parameters, but we can
create multiple versions of a function that call a basic version, as
above.  The compiler I have now chooses the implicit version of the
function always.

I wonder about the following syntax for Param:

implicit varname: Type [=#symbolFilter][=constvalue]

def log(msg: String)(implicit title: String =#logTitle ="No Title")

I can then write:

def func = {
  def inner = {
    implicit val logTitle = "inner";
    log("A message");
  }
  log("Hello");
}

RE: Scala Eclipse Plugin Beta

Sean -- fantastic work on the plugin!  Seems to work very nicely across
everything I've got.  I'll be back in Eclipse, where I belong... ;)

RJ

-----Original Message-----
From: Sean McDirmid [mailto:sean.mcdirmid <at> epfl.ch] 
Sent: Thursday, February 02, 2006 11:57 AM
To: scala <at> listes.epfl.ch
Subject: Scala Eclipse Plugin Beta

Hi,

I'm happy to announce that our Scala Eclipse Plugin (2.1.0) is ready for
public beta testing.

Re: Scala Eclipse Plugin Beta

   I'm one more to congratulate the nice work on the plugin. Unless I
encounter serious errors, Eclipse will be my Scala development
platform from now on. Thank you.

--
[]s, Andrei Formiga

On 2/2/06, Sean McDirmid <sean.mcdirmid <at> epfl.ch> wrote:
> Hi,
>
> I'm happy to announce that our Scala Eclipse Plugin (2.1.0) is ready
> for public beta testing.
>

Re: Bug in Windows Installer (1.4.0.3)

Andrei Formiga <andrei.formiga <at> gmail.com> writes:
>    I just installed Scala 1.4.0.4 in another windows machine and got
> the same problem. I used the automatic installer, added
> %SCALA_HOME%\bin to the path, I can get scalac -version to print the
> correct version, but when I try to compile anything I get the same
> errors. This is the third windows installation I do, all with the same
> problem.

Out of curiosity, have you tried installing to a location that does
not include spaces in the pathname?  That would help narrow down the
problem.

-Lex

avoiding bootclasspath

Re: Bug in Windows Installer (1.4.0.3)

On 03 Feb 2006 16:34:01 +0100, Lex Spoon <lex <at> cc.gatech.edu> wrote:
>
> Out of curiosity, have you tried installing to a location that does
> not include spaces in the pathname?  That would help narrow down the
> problem.

   Yes, I thought about that and tried it, but got the same errors.

--
[]s, Andrei Formiga