Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
JSON in QB64
#1
You all can mostly ignore this. I'm posting this so I don't lose it. However, I'll make a full post once I make it better.

Code: (Select All)
Option Explicit
$NoPrefix
$Console:Only

Print GetEdiSchemaKey("$edi.transactionSets.heading.beginning_segment_for_ship_notice_BSN")

Function GetEdiSchemaKey$ (keyPath As String)
    GetEdiSchemaKey = pipecom_lite("PowerShell -NoProfile $edi = (Get-Content -Path " + Chr$(34) + "C:\Users\zspriggs\Downloads\edi856.json" + Chr$(34) + " ^| ConvertFrom-Json);" + keyPath + " ^| ConvertTo-Json")
End Function

'$Include:'pipecomqb64.bas'
Tread on those who tread on you

Reply
#2
(02-06-2023, 09:26 PM)Balderdash Wrote: You all can mostly ignore this. I'm posting this so I don't lose it. However, I'll make a full post once I make it better.

Are you working on JSONify and stringify for QB64?
That would be most awesome.
Reply
#3
@madscijr I'm not sure about JSONify and stringify but what I'm working on right now is really just parsing JSON with PowerShell. It seems to be going alright, albeit some quirks are present. I might try that JSON C library I found a long time ago but I think it might have been a pain in the butt.
Tread on those who tread on you

Reply
#4
(02-08-2023, 05:25 PM)Balderdash Wrote: @madscijr I'm not sure about JSONify and stringify but what I'm working on right now is really just parsing JSON with PowerShell. It seems to be going alright, albeit some quirks are present. I might try that JSON C library I found a long time ago but I think it might have been a pain in the butt.

Good luck! 

(PS JSONify and stringify for QB64PE would be useful for a lot of things.)
Reply




Users browsing this thread: 1 Guest(s)