On Sun, 2014-10-05 at 19:08 -0700, Paul DeBruicker wrote:
Would using Metacello's knowledge of the platform work for you? e.g.
(MetacelloPlatform current defaultPlatformAttributes includes: '#squeak')
ifTrue:[ ... ]
(MetacelloPlatform current defaultPlatformAttributes includes:
OK.
I think enough has been said. No need to waste more time on it.
I closed the issue.
Thanks Nicolai for making the slice for me!
Best, Jan
On Sat, 2014-10-04 at 21:14 +0100, Jan Vrany wrote:
Hi guys,
I've just opened:
Jan Vrany wrote:
OK.
I think enough has been said. No need to waste more time on it.
I closed the issue.
Thanks Nicolai for making the slice for me!
Best, Jan
Thanks for the attempt. Even though I didn't like the isAxxx pattern,
and feature testing is better, you have me thinking that
2014-10-06 22:26 GMT-03:00 Ben Coman b...@openinworld.com:
DialectsomeWorkingMethod
Transcript show: Dialect myWhoAmI.
What is not to like? :)
Could I reopen that ticket(renamed Introduce dialect testing classes)?
I prefer feature detection, but if you go through this Dialect thing
It’s true that when you do a lot of cross-dialect development, such a method is
often what you desire.
However, I think it’s better to do feature detection instead of dialect
detection. So, something like:
((Smalltalk includesKey: #CharacterWriteStream) ifTrue:[
stream := CharacterWriteStream
Johan Brichau wrote:
It’s true that when you do a lot of cross-dialect development, such a method is
often what you desire.
However, I think it’s better to do feature detection instead of dialect detection.
+1
and others agree... (though on the net its possible to find material to
support
On Sun, 2014-10-05 at 10:29 +0200, Johan Brichau wrote:
It’s true that when you do a lot of cross-dialect development, such a method
is often what you desire.
However, I think it’s better to do feature detection instead of dialect
detection. So, something like:
((Smalltalk includesKey:
Would using Metacello's knowledge of the platform work for you? e.g.
(MetacelloPlatform current defaultPlatformAttributes includes: '#squeak')
ifTrue:[ ... ]
(MetacelloPlatform current defaultPlatformAttributes includes: '#pharo1.2')
.
(MetacelloPlatform current defaultPlatformAttributes
Speaking as the maintainer of an external package (OSProcess/CommandShell) I
agree with both Stef and Johan.
Feature detection is better, because pharo (or squeak, or gemstone) is
meaningless over time as the dialect changes. If you need to test for some
feature, it is better to test for it
Hi guys,
I've just opened:
https://pharo.fogbugz.com/f/cases/14160/Introduce-isXXX-dialect-testing-methods-to-SmalltalkImage-to-ease-cross-dialect-development
Introduce isXXX (isPharo, isVisualWorks, ...) dialect testing methods to
SmalltalkImage to ease multi-dialect development.
RATIONALE:
10 matches
Mail list logo
