Hafiz Naeem-ur-Rehman, the chief of opposition Jamaat-e-Islami party, has told the government to steer clear of passing the controversial bill concerning the age and number of judges, saying it could create 'unnecessary problems.'
In a statement on Thursday, Hafiz Naeem said that national dialogue on Pakistan’s security and future should be the priority, 'not divisive legislation.'
Hafiz Naeem urged the federal and provincial governments to work together and engage Afghanistan in talks for regional peace.
He highlighted the potential for successful negotiations, citing instances like the Laki Marwat and Bannu jirgas.
Hafiz Naeem also criticised the opposition's refusal to engage in dialogue, blaming the government for the 'failure.'
He urged both sides to resume talks for the country’s greater interest, noting that the responsibility rests on them.
"Khan Sahab was negotiating before, but talks have stalled—now, for the nation’s benefit, these conversations must continue," he stated.
He further suggested that an All Parties Conference (APC) should be called to address national issues, including discussions on Balochistan and tribal areas.
Turning to economic matters, Hafiz Naeem stressed the importance of timely oil and LNG imports to save billions and called the Iran-Pakistan gas pipeline project vital for the country.
He expressed frustration with Pakistan’s reluctance to benefit from the deal, comparing it to India and Europe’s willingness to engage in similar agreements.
Hafiz Naeem also criticised the misuse of NAB for political revenge, which he argued led to the economic decline.
He questioned the benefit of NAB's plea bargains, saying they have only filled individuals’ pockets rather than contributing to the national treasury.
In closing, he called for Ali Amin Gandapur to apologise to the nation for his comments, stating that his actions have disrespected journalists and harmed the reputation of the country.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ