[petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Adrian Croucher
hi I just checked out and built the latest PETSc release 3. 21. 4. When I build my code against it, it complains that the recently-introduced PetscObjectIsNull() doesn't seem to exist any more. e. g. : 3677 | if (. not. PetscObjectIsNull(sf)) then ZjQcmQRYFpfptBannerStart

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Barry Smith
You need to have #include in the file above the usage. That is where it is defined. Barry > On Jul 30, 2024, at 8:03 PM, Adrian Croucher > wrote: > > This Message Is From an External Sender > This message came from outside your organization. > hi > > I just checked out and built t

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Adrian Croucher
On 31/07/24 1:25 pm, Barry Smith wrote:    You need to have #include  in the file above the usage.  That is where it is defined. I have: #include Should that not still work? - Adrian   Barry On Jul 30, 2024, at 8:03 PM, Adrian Croucher wrote: This Message Is From an External S

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Adrian Croucher
I just checked the file include/petsc/finclude/petscsys.h, and it contained PetscObjectIsNull() until yesterday, but then it disappeared. - Adrian On 31/07/24 1:27 pm, Adrian Croucher wrote: On 31/07/24 1:25 pm, Barry Smith wrote:    You need to have #include  in the file above the usag

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Adrian Croucher
On 31/07/24 1:47 pm, Adrian Croucher wrote: I just checked the file include/petsc/finclude/petscsys.h, and it contained PetscObjectIsNull() until yesterday, but then it disappeared. It is back in there again in commit 96fb8409 immediately after the 3.21.4 tag. But if you check out 3.21.4 (0

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Barry Smith
>> just checked out and built the latest PETSc release 3.21.4. I should have read your previous email more carefully. All this stuff is in the main git branch, it will not be in release until after September 30. > On Jul 30, 2024, at 9:27 PM, Adrian Croucher > wrote: > > > On 31/07/

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Adrian Croucher
On 31/07/24 2:45 pm, Barry Smith wrote: just checked out and built the latest PETSc release 3.21.4.   I should have read your previous email more carefully.   All this stuff is in the main git branch, it will not be in release until after September 30. Right, according to the terminolo

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Satish Balay
On Wed, 31 Jul 2024, Adrian Croucher wrote: > > On 31/07/24 2: 45 pm, Barry Smith wrote: > > > >>> just checked out and built the latest PETSc release 3. 21. 4. > > > >   I should have read your previous email ZjQcmQRYFpfptBannerStart This Message Is From an External Se

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Satish Balay
On Tue, 30 Jul 2024, Satish Balay wrote: > On Wed, 31 Jul 2024, Adrian Croucher wrote: > > > > > On 31/07/24 2: 45 pm, Barry Smith wrote: > > > > > >>> just checked out and built the latest PETSc release ZjQcmQRYFpfptBannerStart This Message Is From an External Sender

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Adrian Croucher
On 31/07/24 4:47 pm, Satish Balay wrote: Major releases [i.e. 3.21.0, 3.22.0 etc.] are spun from main branch once every 6 months. And bug fix updates [i.e. 3.21.1, 3.21.2 etc.] are spun from release branch once every month [during this 6 month cycle]. i.e PetscObjectIsNull() change that's cu

Re: [petsc-dev] PetscObjectIsNull()

2024-07-30 Thread Pierre Jolivet
> On 31 Jul 2024, at 6:59 AM, Adrian Croucher wrote: > > This Message Is From an External Sender > This message came from outside your organization. > > > On 31/07/24 4:47 pm, Satish Balay wrote: >> >> Major releases [i.e. 3.21.0, 3.22.0 etc.] are spun from main branch once >> every 6 mont