[Pharo-users] Re: ByteString asDate

2022-03-02 Thread Robert Briggs via Pharo-users
at 14:19 To: Any question about pharo is welcome Subject: [Pharo-users] Re: ByteString asDate see chapter 13 in http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf it's a chapter dedicated to exceptions. the #on:do: message is in section 13.4. regarding the asDate

[Pharo-users] Re: ByteString asDate

2022-03-02 Thread Bernardo Ezequiel Contreras
t; *From: *Bernardo Ezequiel Contreras > *Reply to: *Any question about pharo is welcome < > pharo-users@lists.pharo.org> > *Date: *Tuesday, 1 March 2022 at 15:05 > *To: *Any question about pharo is welcome > *Subject: *[Pharo-users] Re: ByteString asDate > > > &

[Pharo-users] Re: ByteString asDate

2022-03-02 Thread Robert Briggs via Pharo-users
of the asDate result, and whether it should self-validate the receiver and raise an exception? Regards R From: Bernardo Ezequiel Contreras Reply to: Any question about pharo is welcome Date: Tuesday, 1 March 2022 at 15:05 To: Any question about pharo is welcome Subject: [Pharo-users] Re: ByteString

[Pharo-users] Re: ByteString asDate

2022-03-01 Thread Bernardo Ezequiel Contreras
try to send the #on:do: message to a block. try this ^ [ (Date readFrom: self pattern: ‘dd/mm/’). true ] on: DateError do: [ false]. On Tue, Mar 1, 2022 at 11:52 AM Robert Briggs via Pharo-users < pharo-users@lists.pharo.org> wrote: > I may be being stupid but the current Date