Setting HAL pins from within NGC subroutines

I know it is possible to read HAL pins from within ngc code (using #<_hal[hal_name]> and FEATURES = <feature mask> in the INI file) since LinuxCNC 2.6.
But is there also a method to set them other than using M6x of defining an M code that executes a script containing 'halcmd setp mypinname value'?

I read up a little about ClassicLadder, but I did not see a method to 'mis-use' it for changing the value of HAL pins from within NGC code?

Mind you, I would just prefer to do it from ngc code. Something like this in a remapped M code:

#<_hal[millturn-mode]> = 2
o100 do
o100 while [#<_hal[millturn-busyflag]> NE 0]

I suppose Parseltongue or just a bash script is more suitable. Or just plain M68 E0 Q2 followed by M66 P0 L2 and making the connections in HAL.

Yes, and so does a line of comment.

I will use M68/M66. That also allows me to wait for a falling edge on a HAL pin and provides a timeout without additional effort. No big deal.

I was just triggered by the following in the documentation :

This feature was motivated by the desire for stronger coupling between user interface components like GladeVCP and PyVCP to act as paramter source for driving NGC file behaviour. The alternative - going through the M6x pins and wiring them - has a limited, non-mmemonic namespace and is unncessary cumbersome just as a UI/Interpreter communications mechanism.

That made me think that there could also be an alternate method to do ngc->HAL communication.