My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
answer:
no they are not. This seems to be something new where they can be readonly, but I just pulled one from getCwd and it was manipualable.
hmmm..
---- On Tue, 11 Jul 2023 15:27:46 -0400 gettimothy via Squeak-dev squeak-dev@lists.squeakfoundation.org wrote ---
My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
It looks like you need to examine methods like -
Object>>#beWritableObject Object>>#setIsReadOnlyObject: Object>>#attemptToAssign:withIndex: Context>>#modificationForbiddenFor:instVarAt:put: and the ModificationForbidden class.
As an example (that does pretty much what I expect but may not be strictly proper!) -
['dofigjdfgoidfdog' at: 5 put: $T; yourself] on: ModificationForbidden do: [:ex| ex object beWritableObject. ex retryModification]
If you know that you are going to madify something you might use
'dofigjdfgoidfdog' beWritableObject; at: 5 put: $T; yourself
On 2023-07-11, at 12:27 PM, gettimothy via Squeak-dev squeak-dev@lists.squeakfoundation.org wrote:
My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim "Bo***x" said Pooh when Piglet kneed him in the groin.
String literals -- e.g., the ones you can put in code -- are read-only by default. Dynamically constructed strings -- e.g., via #streamContents: -- are still writable. Change it via #beWritableObject if needed. Yet, better keep literal strings (and symbols) read-only. There used to be a time where those where cached in the CompiledMethod.
Best, Marcel Am 11.07.2023 15:26:16 schrieb Tim Rowledge tim@rowledge.org: It looks like you need to examine methods like -
Object>>#beWritableObject Object>>#setIsReadOnlyObject: Object>>#attemptToAssign:withIndex: Context>>#modificationForbiddenFor:instVarAt:put: and the ModificationForbidden class.
As an example (that does pretty much what I expect but may not be strictly proper!) -
['dofigjdfgoidfdog' at: 5 put: $T; yourself] on: ModificationForbidden do: [:ex| ex object beWritableObject. ex retryModification]
If you know that you are going to madify something you might use
'dofigjdfgoidfdog' beWritableObject; at: 5 put: $T; yourself
On 2023-07-11, at 12:27 PM, gettimothy via Squeak-dev wrote:
My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim "Bo***x" said Pooh when Piglet kneed him in the groin.
thank you.
---- On Tue, 11 Jul 2023 19:00:39 -0400 Marcel Taeumel via Squeak-dev squeak-dev@lists.squeakfoundation.org wrote ---
String literals -- e.g., the ones you can put in code -- are read-only by default. Dynamically constructed strings -- e.g., via #streamContents: -- are still writable. Change it via #beWritableObject if needed. Yet, better keep literal strings (and symbols) read-only. There used to be a time where those where cached in the CompiledMethod.
Best,
Marcel
Am 11.07.2023 15:26:16 schrieb Tim Rowledge mailto:tim@rowledge.org:
It looks like you need to examine methods like -
Object>>#beWritableObject Object>>#setIsReadOnlyObject: Object>>#attemptToAssign:withIndex: Context>>#modificationForbiddenFor:instVarAt:put: and the ModificationForbidden class.
As an example (that does pretty much what I expect but may not be strictly proper!) -
['dofigjdfgoidfdog' at: 5 put: $T; yourself] on: ModificationForbidden do: [:ex| ex object beWritableObject. ex retryModification]
If you know that you are going to madify something you might use
'dofigjdfgoidfdog' beWritableObject; at: 5 put: $T; yourself
On 2023-07-11, at 12:27 PM, gettimothy via Squeak-dev wrote:
My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
tim
On Tue, Jul 11, 2023 at 03:27:46PM -0400, gettimothy via Squeak-dev wrote:
My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
??seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
It looks like this to my on my Linux box:
(UnixProcessAccessorTestCase selector: #testArgsAsFlatArrayAndOffsets) run => 1 run in 0:00:00:00, 1 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes
Is there a preference setting involved? I'm not seeing the issue.
Dave
Interesting, I do not know.
I had to go "one lower" in the image because I was getting some frustrating errors on some installs.
I will try upgrading Squeak and see what happens.
Image
-----
Squeak6.1alpha
latest update: #22667
Current Change Set: HomeProject
Image format 68021 (64 bit)
Preferred bytecode set: SistaV1
Virtual Machine
---------------
Open Smalltalk Cog[Spur] VM [CoInterpreterPrimitives VMMaker.oscog-dtl.3185]
Unix built on Jun 2 2022 15:26:05 Compiler: Clang 9.0.0 (tags/RELEASE_900/final)
platform sources revision VM: 202206021410 runner@fv-az125-921:work/opensmalltalk-vm/opensmalltalk-vm Date: Thu Jun 2 16:10:44 2022 CommitHash: c9fd365 Plugins: 202206021410 runner@fv-az125-921:work/opensmalltalk-vm/opensmalltalk-vm
CoInterpreter VMMaker.oscog-dtl.3185 uuid: 0e7f07b8-eed6-4362-b223-86c98594ddb9 Jun 2 2022
StackToRegisterMappingCogit VMMaker.oscog-mt.3179 uuid: c6fbcb07-2a19-ed4f-8b40-9c119a70882a Jun 2 2022
---- On Wed, 12 Jul 2023 21:12:57 -0400 David T. Lewis lewis@mail.msen.com wrote ---
On Tue, Jul 11, 2023 at 03:27:46PM -0400, gettimothy via Squeak-dev wrote:
My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
??seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
It looks like this to my on my Linux box:
(UnixProcessAccessorTestCase selector: #testArgsAsFlatArrayAndOffsets) run => 1 run in 0:00:00:00, 1 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes
Is there a preference setting involved? I'm not seeing the issue.
Dave
Hi
I had chosen to install a prior version of squeak because the Preferences Browser was errorring out on the Monticello install.
Just now, I downloaded the latest (same error in Proferences Browser) but I x-ed it and installed stuff manually.
Here is the latest version.
676-64bit.image
Squeak6.1alpha
latest update: #22676
Current Change Set: HomeProject
Image format 68533 (64 bit)
Preferred bytecode set: SistaV1
Virtual Machine
---------------
Open Smalltalk Cog[Spur] VM [CoInterpreterPrimitives VMMaker.oscog-dtl.3185]
Unix built on Jun 2 2022 15:26:05 Compiler: Clang 9.0.0 (tags/RELEASE_900/final)
platform sources revision VM: 202206021410 runner@fv-az125-921:work/opensmalltalk-vm/opensmalltalk-vm Date: Thu Jun 2 16:10:44 2022 CommitHash: c9fd365 Plugins: 202206021410 runner@fv-az125-921:work/opensmalltalk-vm/opensmalltalk-vm
CoInterpreter VMMaker.oscog-dtl.3185 uuid: 0e7f07b8-eed6-4362-b223-86c98594ddb9 Jun 2 2022
StackToRegisterMappingCogit VMMaker.oscog-mt.3179 uuid: c6fbcb07-2a19-ed4f-8b40-9c119a70882a Jun 2 2022
I doubt that prior installs are the issue, but II have installed the following
MCHttpRepository
location: 'http://www.squeaksource.com/PostgresV3'
user: ''
password: ''
just load the latest update
Metacello new
baseline:'Seaside3';
repository: 'github://SeasideSt/Seaside:master/repository';
load
Apps->SeasideControlPanel (stop service, change port if needed, etc)
bug in WAFormInputTag chage asSelector asMutator to asSelector asSimpleSetter
Installer ss
project: 'MetacelloRepository';
install: 'ConfigurationOfOSProcess'.
(Smalltalk at: #ConfigurationOfOSProcess) load
and then I ran the OSProcess tests...
same error.
three failures too.
I have not installed CommandShell.
hth.
---- On Wed, 12 Jul 2023 21:12:57 -0400 David T. Lewis lewis@mail.msen.com wrote ---
On Tue, Jul 11, 2023 at 03:27:46PM -0400, gettimothy via Squeak-dev wrote:
My apologies if they always have been.
UnixProccessAccessorTestCase >> #testArgsAsFlatArrayAndOffsets
errors out on an attempt to modify a character in a ByteString.
??seems odd as I seem to recall being able to modify strings in the past.
cordially,
tty
It looks like this to my on my Linux box:
(UnixProcessAccessorTestCase selector: #testArgsAsFlatArrayAndOffsets) run => 1 run in 0:00:00:00, 1 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes
Is there a preference setting involved? I'm not seeing the issue.
Dave
I had to implement Symbol>>#asMutator in a very similar set of installations - Seaside, Postgresql & OSprocess.
On 2023-07-13, at 5:17 AM, gettimothy via Squeak-dev squeak-dev@lists.squeakfoundation.org wrote:
Apps->SeasideControlPanel (stop service, change port if needed, etc) bug in WAFormInputTag chage asSelector asMutator to asSelector asSimpleSetter
asMutator "Return a setter message from a getter message. For example, #name asMutator returns #name: Temporary over-ride until Seaside 3.5 release" ^self asSimpleSetter
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim "Bother!" said Pooh, as Piglet pressed <START> on the Microwave...
I had to implement Symbol>>#asMutator in a very similar set of installations - Seaside, Postgresql & OSprocess.
Hmm... it's still present in 5.3, 6.0, and 6.1alpha ... there was only a short period of time when we removed this or put it into deprecation or something. Hmm...
Best, Marcel Am 13.07.2023 18:46:47 schrieb Tim Rowledge tim@rowledge.org: I had to implement Symbol>>#asMutator in a very similar set of installations - Seaside, Postgresql & OSprocess.
On 2023-07-13, at 5:17 AM, gettimothy via Squeak-dev wrote:
Apps->SeasideControlPanel (stop service, change port if needed, etc) bug in WAFormInputTag chage asSelector asMutator to asSelector asSimpleSetter
asMutator "Return a setter message from a getter message. For example, #name asMutator returns #name: Temporary over-ride until Seaside 3.5 release" ^self asSimpleSetter
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim "Bother!" said Pooh, as Piglet pressed on the Microwave...
That asMutator thing is from some very old notes.
I did not have to do that on this install.
sorry for the confusion, I don't know why I copy-n-pasted that into the email.
t
---- On Fri, 14 Jul 2023 03:29:26 -0400 Marcel Taeumel via Squeak-dev squeak-dev@lists.squeakfoundation.org wrote ---
I had to implement Symbol>>#asMutator in a very similar set of installations - Seaside, Postgresql & OSprocess.
Hmm... it's still present in 5.3, 6.0, and 6.1alpha ... there was only a short period of time when we removed this or put it into deprecation or something. Hmm...
Best,
Marcel
Am 13.07.2023 18:46:47 schrieb Tim Rowledge mailto:tim@rowledge.org:
I had to implement Symbol>>#asMutator in a very similar set of installations - Seaside, Postgresql & OSprocess.
On 2023-07-13, at 5:17 AM, gettimothy via Squeak-dev wrote:
Apps->SeasideControlPanel (stop service, change port if needed, etc) bug in WAFormInputTag chage asSelector asMutator to asSelector asSimpleSetter
asMutator "Return a setter message from a getter message. For example, #name asMutator returns #name: Temporary over-ride until Seaside 3.5 release" ^self asSimpleSetter
tim
On 2023-07-14, at 12:29 AM, Marcel Taeumel via Squeak-dev squeak-dev@lists.squeakfoundation.org wrote:
I had to implement Symbol>>#asMutator in a very similar set of installations - Seaside, Postgresql & OSprocess.
Hmm... it's still present in 5.3, 6.0, and 6.1alpha ... there was only a short period of time when we removed this or put it into deprecation or something. Hmm...
Yeah, it got deprecated for 5.3, which meant having to set the preference to not alert about deprecations, which is why I did an override for work image building
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Compromise, says Prof. Trefusis, is stalling between two fools
squeak-dev@lists.squeakfoundation.org
-
David T. Lewis -
gettimothy -
Marcel Taeumel -
Tim Rowledge