Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I like your assessment of LabVIEW. I find that if your code is turning to spaghetti, you're not using enough sub-VIs. Try to find blocks of code that accomplish one thing and put that code in its own VI. As a bonus you get to design a little icon for your new sub-VI. :)

Your "rabbit hole" analogy is spot-on and I'm not sure how NI can address some of those problems. Some things like Ctags that are so valuable in text-based languages just seem to have no obvious analogy in a graphical programming language... it's fun to imagine though.

(Caveat, chemist talking about programming)



If you right click a VI in a LabVIEW project you can "Find Callers" and "Find SubVIs"

I'm using LV 2009, I'm not sure what version this was added.


I'm sure part of the issue was that I was trying to teach myself Labview under a deadline as a fresh college grad with zero oversight from anyone with experience with it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: