Title: | DEC Pascal Notes |
Notice: | See note 1 for kits. Bug reports to CLT::DEC_PASCAL_BUGS |
Moderator: | TLE::REAGAN |
Created: | Sat Jan 25 1986 |
Last Modified: | Tue Jun 03 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2675 |
Total number of notes: | 13409 |
I am working with a customer that has some old VAX Pascal code that we are trying to convince them to migrate to an alpha system. They haven't touched the code since they tried to migrate from VAX Pascal V3.6 to V4.0 a long time ago. They weren't able to compile with V4.0 due to naming conflicts. They use the same name for procedures, environments, and global record definitions. They saw this as a bug in V4.0, but I see it as enforcing something that V3.6 let go. Will this naming conflict still a problem in V5.5?
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2671.1 | TLE::REAGAN | All of this chaos makes perfect sense | Fri May 02 1997 16:44 | 3 | |
Uh, what naming conflict? Can you give me a small example? -John | |||||
2671.2 | BIGCHZ::EZZELL | Mike Ezzell | Mon May 05 1997 11:16 | 7 | |
Its been a while since they tried to upgrade to V4.0, so they were not able to give me the error messages. The example that they gave me had the procedure named MOVER and an environment file named MOVER.PEN. When MOVER.PEN is inherited, the conflict occured. I don't know PASCAL, I am passing on what the customer told me. Does this make sense? | |||||
2671.3 | TLE::REAGAN | All of this chaos makes perfect sense | Mon May 05 1997 14:09 | 4 | |
That isn't enough information to tell anything. They will have to give me some more details before I can figure anything out. -John |