[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Different dialects under the same root
- To: Derick Eddington <derick.eddington@xxxxxxxxx>
- Subject: Re: Different dialects under the same root
- From: Vitaly Magerya <vmagerya@xxxxxxxxx>
- Date: Sat, 12 Dec 2009 14:16:07 +0200
- Cc: srfi-103@xxxxxxxxxxxxxxxxx
- Delivered-to: srfi-103@xxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=DtymVmiYna+LtSLHNj0js60IBT3wHUGRKKYFNZ2M/AE=; b=hIoxUuygDoUoqWgCrXqDS6CKyKrnrivWpojKX6/BEP/b+ed31/9VmEQmknsafRoPGl jIgkfxm9iipOXM4PLjpAyZzLoqHESb0q9cNd5KgoqOFcnXw2ULtm0RF0lqVUuw/6wi+c xuOyDxYThdb+qNZoJoGqkmoWMYu2Dd+vYs70Y=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=AdMZXeEiwqweao2vPJXjeNxWboe9x4dLTOQJh6uVMYTbzCFm+Ev2PZ71gCKLet1ptD 1TsRHg/g3Saga68u6hc+RWCGvDYUXHUN91kfdty/ERPSeAqemRIOzwF/qgdlSxhzgzV+ BFE7/ewSzqZaAHjtHwW79WlcS83Hw0Obw0u8o=
- In-reply-to: <1260582209.2650.104.camel@eep>
- References: <4B226D34.7040506@xxxxxxxxxxx> <4B2289BF.4050304@xxxxxxxxx> <1260582209.2650.104.camel@eep>
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091130 Thunderbird/3.0
Derick Eddington wrote:
> With the previous revision which didn't support different file name
> extensions for different dialects, different dialects could not share
> the search paths environment variable because different dialects would
> be using the same extension and so a file for one dialect could
> unavoidably shadow a file for another dialect. With different
> extensions, that problem doesn't exist and different dialects can
> share the environment variable.
OK, now I think I got it. Different extensions for implementations are
introduced not to be able to put different implementation-specific
libraries into the exact same folder (which was my objection), but to
resolve shadowing which may occur when SCHEME_LIB_PATH lists several paths.